Task #3755

Concurrency stress testing and cache mechanism

Added by Robert Lemke about 6 years ago. Updated almost 5 years ago.

Status:New Start date:2009-06-25
Priority:Must have Due date:
Assigned To:- % Done:

0%

Category:- Testing -
Target version:-
Sprint: Has patch:
PHP Version: Complexity:

Description

After the first experiences and results from #3582 we need to do some more thorough stress testing to identify race conditions in FLOW3, especially in the caching mechanism. We need to assure that especially the code caches cannot be built multiple times simultaneously which currently is seems to be not always the case.


Related issues

related to TYPO3.Flow - Task #3582: Concurrency stress test Closed 2009-06-05
related to TYPO3.Flow - Bug #28733: Implement LockManager for avoiding Race Conditions Resolved 2011-08-04
related to TYPO3.Flow - Bug #27989: Wrong check in our atomic writes code Resolved 2011-07-08

History

#1 Updated by Robert Lemke about 6 years ago

  • Target version deleted (283)

#2 Updated by Karsten Dambekalns over 5 years ago

  • Target version set to 1.0 alpha 8

#3 Updated by Robert Lemke over 5 years ago

  • Target version changed from 1.0 alpha 8 to 1.0 alpha 9

#4 Updated by Robert Lemke about 5 years ago

  • Target version deleted (1.0 alpha 9)

Also available in: Atom PDF