Task #3755

Concurrency stress testing and cache mechanism

Added by Robert Lemke almost 12 years ago. Updated over 10 years ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
- Testing -
Target version:
-
Start date:
2009-06-25
Due date:
% Done:

0%

Estimated time:
Sprint:
PHP Version:
Has patch:
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 testClosedRobert Lemke2009-06-05

Actions
Related to TYPO3.Flow - Bug #28733: Implement LockManager for avoiding Race ConditionsResolved2011-08-04

Actions
Related to TYPO3.Flow - Bug #27989: Wrong check in our atomic writes codeResolvedKarsten Dambekalns2011-07-08

Actions
#1

Updated by Robert Lemke almost 12 years ago

  • Target version deleted (283)
#2

Updated by Karsten Dambekalns over 11 years ago

  • Target version set to 1.0 alpha 8
#3

Updated by Robert Lemke about 11 years ago

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

Updated by Robert Lemke almost 11 years ago

  • Target version deleted (1.0 alpha 9)

Also available in: Atom PDF