Issue Summary

CCMA performance may be impaired in specific circumstances if there are multiple Confluence administrators viewing a large migration plan.

When a CCMA plan is being viewed, CCMA polls the Confluence database approximately every 5 seconds for a near real-time view.

It has been discovered that if multiple Confluence administrators are concurrently viewing the same plan, CCMA performance is hampered significantly, as each user is polling the database, diverting resources from critical CCMA tasks.

Steps to Reproduce

1. Create a Confluence site with 2000 spaces.
2. Create a CCMA migration plan with 2000 spaces.
3. Execute the CCMA plan.
4. Assign 9 other users Confluence administrator rights.
5. For each user, open up the same migration plan.

If needed (for replication purposes):

• (for every user) open up a second tab in incognito mode, in another browser engine, or both.
• limit database and app node resources to below recommended size (see Infrastructure recommendations for enterprise Confluence instances on AWS).
• increase user count to >20.000
• increase group count to >10.000
• increase space count to >5.000
• increase content and attachment count to >10.000.000

Expected Results

CCMA performance is stable.

Actual Results

CCMA speed decreases significantly, by up to a factor of 10.

Workaround

Do not monitor CCMA in many sessions.

• Limit monitoring by closing the CCMA plan and periodically opening the browser tab if needed.
• Limit monitoring to a single browser session to avoid a self-inflicted denial of service attack. If necessary, share the screen through other means (Zoom/Teams). If possible, this user should also periodically check progress.
• Monitor database performance through existing database monitoring tools.