UX performance of staging with versionning and branching enabled is poor when the site becomes large

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2
• Fix Version/s: 6.1.30 EE GA3, 6.2.0 CE M6
• Component/s: Content Publishing > Staging
• Labels:
  • QA-R
  • QA-TP
  • ee-ts
• Environment: Any
• Branch Version/s:
  6.1.x
• Backported to Branch:
  Committed
• Story Points: 2
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/11698

The amount of coordination required to track and select layout revisions results in a significant number of DB operations some of which are not well optimized, or simply cause caches to churn (lots of misses, or more insertions than max elements) when not well tuned. Also, since the coordination is handled by proxies, repeated creation of proxies produces lots of expensive overhead.