[PUBLISHING-246] extend definition configuration with Interactive publishing to avoid performance issues Created: 10/Jul/23 Updated: 18/Sep/23 |
|
| Status: | Open |
| Project: | Publishing |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
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 | ||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||
| Description |
Steps to reproducea] Publish a recursively huge subtree with just a few modified items Expected results (ideas)let the user know that publishing too many nodes can cause freezing the screen and performance issues / slowing down of app and provide the possibility to avoid too big publishing load
Proposals a] in case of publishing big amount of nodes in recursive mode (publishing including sub-nodes) - User is offered a dialog where he sees the publication options like in the screen below ( "Modified items (number) vs "Bulk (utilizing itemsPerRequest)") so he can pick the most reasonable one. The recommended one might be preselected.
For operation: Publish Inc. subpages adapt the dialog so the user can access all necessary information while selecting one of the options. This problem occurs only with big-size projects so make sure to make this functionality available not by default but by enabling it via definition.
Help tips:
Actual resultsUser is not warned in case of
Workaround
Development notes |
| Comments |
| Comment by Dominik Maslanka [ 12/Jul/23 ] |
|
Proposals: Questions from the team: |