Task #3582

Concurrency stress test

Added by Robert Lemke over 12 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
- Testing -
Start date:
2009-06-05
Due date:
% Done:

100%

Estimated time:
Sprint:
PHP Version:
Has patch:
Complexity:

Description

Currently we have only few experience with multiple concurrent users accessing FLOW3 at the same time. This ticket is about testing the behavior of FLOW3 when running simultaneous requests.

What we especially need to find out is

  • how FLOW3 reacts if caches are empty
  • how FLOW3 reacts in production context if caches are filled (theoretically shouldn't be a problem at all)
  • if accessing FLOW3 in development context has any side effects on the Production context (shouldn't ...)
  • how FLOW3 scales performance wise

Try to detect any race conditions so we can make them atomic.


Related issues

Related to TYPO3.Flow - Feature #3581: Site lock / code cache flushing mechanismResolvedRobert Lemke2009-06-05

Actions
Related to TYPO3.Flow - Task #3755: Concurrency stress testing and cache mechanismNew2009-06-25

Actions

Also available in: Atom PDF