[PUBLISHING-134] orderSiblings causes the nodes ordering process took minutes to finish Created: 07/Mar/22 Updated: 14/Sep/23 Resolved: 14/Sep/23 |
|
| Status: | Closed |
| Project: | Publishing |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.10 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Minh Nguyen | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Visible to: |
Annick Boehler
|
||||||||||||||||
| Epic Link: | Performance problems with too many child nodes | ||||||||||||||||
| Team: | |||||||||||||||||
| Description |
|
Steps to reproduce .... /profile15000 3. choose 1 profile to publish. It will take minutes to finish so when publishers publish another node may encounter a locking issue. Expected results Actual results Development notes: 2nd try: |
| Comments |
| Comment by Roman Kovařík [ 21/Mar/22 ] |
|
Discovery: Document known limitations for big flat structures in JCR trees |
| Comment by Pierre Sandrin [ 21/Mar/22 ] |
|
Hi @Roman We run into a similar Problem where we have a Folder containing about 1500+ nodes. When publishing the folder it takes a long time and the CPU usages is rising. After 10 - 15 min. the public instances are not reachable anymore and the publication process is aborted. (DX-Core with 2 Publics) You mentioned limitations of JCR for big flat structures. Could you describe those limitations shortly, since I have no access to that support issue you linked to. Now, we cannot turn off ordering of sibling for all workspaces since it is crucial for the pages workspace. Would it be a solution generate subdirectories where we put nodes starting with A, B, C, ... It would reduce the ampout of nodes top a few hundreds. Thanks a lot! |
| Comment by Roman Kovařík [ 22/Mar/22 ] |
|
Hi Pierre
Here is a copy:
That would definitively help, it's worth trying. If that won't be enough, we can consider this suggestion:
I hope that helps Roman |
| Comment by Roman Kovařík [ 03/May/23 ] |
|
For the record, for apps without a workflow, most of the ordering can be avoided utilising https://docs.magnolia-cms.com/product-docs/6.2/Modules/List-of-modules/Publishing-module.html#_configuring_itemsperrequest. But again, only in case of a tree structure respecting the Jackrabbit recommendations.
|
| Comment by Dominik Maslanka [ 14/Sep/23 ] |
|
This issue is solved by introducing a fast/full ordering configuration that will support ordering on public instance: https://jira.magnolia-cms.com/browse/PUBLISHING-254 |