[PUBLISHING-294] Create a recommendation for structuring nodes in particular order to avoid unnecessary performance issues Created: 13/Sep/23 Updated: 10/Oct/23 Resolved: 29/Sep/23 |
|
| Status: | Closed |
| Project: | Publishing |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Dominik Maslanka | Assignee: | Adrian Brooks |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||
| Template: |
|
|||||||||||||||
| Acceptance criteria: |
Empty
|
|||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
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: | ||||||||||||||||
| Epic Link: | Performance problems with too many child nodes | |||||||||||||||
| Sprint: | Nucleus 46 | |||||||||||||||
| Story Points: | 1 | |||||||||||||||
| Team: | ||||||||||||||||
| Work Started: | ||||||||||||||||
| Description |
|
As an author, I want to know and be sure that the pages I know how to create and structure pages in the best performant way so that after creating a bigger amount, I will not face any performance issues.
Description: Create a recommendation tooltip for an author that would suggest the author not create too many items at the same level because a bigger amount of nodes published at the same level can cause performance issues: here are suggestions of pages where such help tips could appear: https://docs.magnolia-cms.com/product-docs/6.2/Administration/Architecture/Publishing.html https://docs.magnolia-cms.com/product-docs/6.2/Authoring/Publishing.html
Reason: Keep the repository lean and clean: a bloated repository negatively impacts overall performance, particularly search. Jackrabbit is optimized for hierarchical content and does not handle flat structures well. To ensure optimal performance, we need to break flat structures into a hierarchy. Features that constantly create content (such as Messages, Tasks, and Versions) should have a way to clean up old content. |