[PUBLISHING-254] Reduce the publishing load by optimizing ordering on the public instance Created: 13/Jul/23 Updated: 18/Sep/23 Resolved: 11/Sep/23 |
|
| Status: | Closed |
| Project: | Publishing |
| Component/s: | None |
| Affects Version/s: | 1.3.10 |
| Fix Version/s: | 1.4.0, 1.3.12 |
| Type: | Improvement | Priority: | Normal |
| Reporter: | Dominik Maslanka | Assignee: | Antonín Juran |
| Resolution: | Done | Votes: | 0 |
| Labels: | VN-Testing | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | 7.5h | Time Spent: | 7.5h |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Attachments: |
|
|||||||||||||||||||||||||||||||||||||||||||||
| 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)
|
|||||||||||||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
|||||||||||||||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
|||||||||||||||||||||||||||||||||||||||||||||
| Date of First Response: | ||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Performance problems with too many child nodes | |||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Nucleus 43, Nucleus 44 | |||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 5 | |||||||||||||||||||||||||||||||||||||||||||||
| Team: | ||||||||||||||||||||||||||||||||||||||||||||||
| Work Started: | ||||||||||||||||||||||||||||||||||||||||||||||
| Approved: |
Yes
|
|||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Antonín Juran [ 25/Jul/23 ] |
DISCOVERYSuggested solution (bypassing imported nodes) could be easy implemented in publishing-receiver module see example here. Configuration of bypassOrderingVoters could be done similar way as in attached config.yaml on /modules/publishing-core/config path. |
| Comment by Adrian Brooks [ 29/Aug/23 ] |
|
Moved from sprint 43 to sprint 44. 2 SP done, and 3 SP left to do. |
| Comment by Quach Hao Thien [ 11/Sep/23 ] |
Solutions:Allow users to config the ordering options: none, fast, full in PublicationCommand via Command's params There is one case left: ordering by fast option would be tackled in
|
| Comment by Julie Legendre [ 11/Sep/23 ] |
|
Hi all, would it make sense to improve the the title of this ticket to indicate what has been done (spotted when working on the 6.2.39 RN)? |