[MAGNOLIA-2151] workflow: test memory consuming Created: 23/May/08  Updated: 23/Jan/13  Resolved: 25/Jul/08

Status: Closed
Project: Magnolia
Component/s: workflow
Affects Version/s: 3.6 RC1
Fix Version/s: 3.6

Type: Task Priority: Critical
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File memory usage.jpg     JPEG File screenshot-1.jpg    
Issue Links:
Cloners
is cloned by MAGNOLIA-2172 workflow: unexpected modified item st... Closed
dependency
is depended upon by MAGNOLIA-2150 port critical changes done for 3.5.7 Closed
relation
is related to MAGNOLIA-1148 [wf] workflow item reminants left be... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

All memory related tests have been done without workflow. We should verify that too.



 Comments   
Comment by Philipp Bracher [ 28/May/08 ]
  • both author and public in a single tomcat
  • 128M assigned
  • external h2 with bundled PM
  • test run ~ 1 hour
  • 110'000 request (25/s) including login, editing, activation, view inbox, publishing, deleting
  • 2'500 pages created
  • 21'000 paragraphs created

It looks quite nice. Nevertheless we have to do the same test for 24 hours when we have a first stable version

Comment by Alvaro Arce [ 24/Jul/08 ]
  • Magnolia 3.6 RC4
  • both author and public in a single tomcat
  • JVM with options -Xms64M -Xmx512M -
  • external mySQL, external Blobs
  • Activation of the whole tree with workflow asigned
  • 272 pages activated
  • 54 minutes to activate (workflow + activation + cache flushed) the whole site
Generated at Mon Feb 12 03:33:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.