-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
Steps to reproduce
1. Create a groovy script to create ~15k nodes under root /
Example: create new workspace profile
/profile1
/profile2
....
/profile15000
2. Make sure orderSiblings=true on author and public instances (/.magnolia/admincentral#app:configuration:browser;/modules/publishing-core/config@orderSiblings:treeview
3. choose 1 profile to publish. It will take minutes to finish
4. This process can cause a locked path:
Example logging: info.magnolia.publishing.locking.PathLockManager : Lock for path [internalProfiles] requested by thread [Thread[http-nio-8080-exec-229,5,main]] with id [781].
so when publishers publish another node may encounter a locking issue.
Expected results
1. The publishing should be done quickly.
2. or the orderSiblings can be configured enable/disable per workspace
Actual results
1. Take minutes to finish publishing 1 node
2. If we try publish another node, we may encounter a locking issue
Development notes:
1. I enable debug mode for publishing process on public
2. Current customer's internalProfile workspace has ~13k nodes.
3. publish ~3-10 nodes:
4. I got 279k debug message saying
receiver.operation.jcr.AbstractJcrReceiveOperation: Ordering S5YRAK_ before S5ZZ24_
2nd try:
1. Current customer's internalProfile workspace has ~13k nodes.
2. I publish 1 node, It took Mar 8, 3:47 am – Mar 8, 3:53 am, => ~6 minutes to finish ordering
3.
4. Exported logging: extract-2022-03-08T05_04_52.914Z.csv
- documents
-
MAGNOLIA-8880 Performance problems with too many child nodes
- Open
- relates to
-
MAGNOLIA-9053 Improve scalabity of publishing content
- Open