-
Improvement
-
Resolution: Done
-
Normal
-
1.3.10
-
-
Empty show more show less
-
Yes
-
Yes
-
Nucleus 43, Nucleus 44
-
5
-
Yes
User Story: as a developer, I would like to optimize concurrent node publishing to reduce performance issues with publishing too many nodes simultaneously.
Context: Code provided to the customer is proposal for optimizing publishing of too many nodes at the same time on the same level.
customer is using PostgreSQL as storage and with limitations for too big flat structures in JCR trees he was trying to publish
Acceptance criteria
- is related to
-
PUBLISHING-285 Published node is not placed at correct position if fast ordering is configured
- Closed
- relates to
-
MAGNOLIA-9053 Improve scalabity of publishing content
- Open
1.
|
Implementation | Completed | Antonín Juran | |
2.
|
Code review | Completed | Adam Siska | |
3.
|
Pre-integration QA | Completed | Adam Siska | |
4.
|
Final QA | Completed | Quach Hao Thien | |
5.
|
Write unit tests | Completed | Antonín Juran | |
6.
|
DOCu | Closed | Antonín Juran | |
7.
|
Docu rv | Completed | Adrian Brooks | |
8.
|
2nd rv/piQA - Deprecation of orderSiblings | Completed | Adam Siska |