We're experiencing the problem that seems to be documented in the tagged question, but the solution provided has consequences in VMWare where disabling memory ballooning causes performance issues for the physical host, thus affecting other unrelated servers.
Is there any other suggestion that can be offered? Would increased RAM help (even though it's the CPU that's pegged, not the memory)? Adding another CPU (or will it run away with both)?
As best I understand this has something to do with Java garbage collection - is there any configuration change I can make or process I can trigger to overcome the more pinpointed issue?
Will need some additional information. How big is your Confluence Site, to include number of pages (current version and all versions), number of users (total and concurrent), Confluence Version, Java Version, Number of CPU's, amount of RAM, and the JVM arguments from the setenv file.
Feel free to clean out any sensitive information from those, but don't hide any relevant info.
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events