[PUBLISHING-247] DOC: Add a "Publishing performance" page Created: 11/Jul/23  Updated: 24/Aug/23  Resolved: 11/Aug/23

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Adrian Brooks 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:
Relates
relates to PUBLISHING-246 extend definition configuration with ... Open
Sub-Tasks:
Key
Summary
Type
Status
Assignee
PUBLISHING-265 DOC: First draft Sub-task Completed Adrian Brooks  
PUBLISHING-266 DOC: Review Sub-task Completed Adrian Brooks  
PUBLISHING-267 DOC: First revision Sub-task Completed Adrian Brooks  
PUBLISHING-268 DOC: SOC2 approval Sub-task Completed Dominik Maslanka  
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)
Epic Link: Performance problems with too many child nodes
Sprint: Nucleus 42
Story Points: 3
Team: Nucleus
Work Started:
Approved:
Yes

 Description   

“Publishing performance” page in the Administration section below the “Publishing overview” node. And for the structure, something like this:

What are you publishing?

  • Selective pages versus republishing the entire tree -> publish only the necessary pages to optimize performance.
  • Creating a balanced tree for bulk publishing with itemsPerRequest -> Visualize a balanced tree and explain when itemsPerRequest could improve performance (i.e., itemsPerRequest = number of nodes in the folder). Link to the existing Publishing module documentation of itemsPerRequest here.

How can vacuuming dead nodes in PostgreSQL’s main and toast tables affect performance?

  • Adjust autovacuum operations -> link to the existing database modifications documentation section here.

How can I tweak the publishing workflow on the public instance?

  • Ordering of siblings -> Turn off ordering on the public instance [link to existing publishing workflow section here.

Generated at Mon Feb 12 10:36:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.