[MAGNOLIA-329] Activation performance Created: 17/Apr/05  Updated: 10/May/05  Resolved: 10/May/05

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 2.1 Final
Fix Version/s: 2.1 Final

Type: Bug Priority: Major
Reporter: Fabrizio Giustina Assignee: Sameer Charles
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Activation is actually really slow and requires a lot of memory... we need to profile the process to find memory leaks.
Anybody ever tried to do this? Any hint on where memory/time is lost?



 Comments   
Comment by Sameer Charles [ 17/Apr/05 ]

I did some tests before, actual data transfer is quite fast but it takes quite a lot of time while
persisting data, I have tested with jackrabbit ObjectPersistenceManager/CQFS

I have a same problem if I delete and create simultaneously few pages in memory and try to persist them all at once. I am pretty sure its a problem in persistence manager, l am currently testing crx from Day will let you know abouzt my findings.
also ll look at the activation code.

Comment by Sameer Charles [ 10/May/05 ]

after re-factoring and changes in NodeData storage definition save is quite fast resulting in much faster content activation.

Generated at Mon Feb 12 03:16:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.