We are planning a large (Enterprise scale) Jira instance, based on the sizing guidence from Atlassian. The server is equipped with more than 128 GB of memory.
During a recent planning session, a developer noted that JVM's larger than 8 GB can have performance issues due to garbage collection, and other memory management, taking too long.
Has anyone configured a JVM with large memory (64 GB and up) and experienced this type of issue, and was there any remedy?
Hi Jim, do you anticipate a need for JIRA having >64GB of memory set for the heap? It's quite a rare situation even in large organizations. We've had instances running with >8GB of RAM.
Whilst garbage collection would be consideribly slower, you'd also require less garbage collection (as you'll less often fill up all the memory). I'd consider using Java 7 and G1C as a concurrent garbage collector to avoid any huge performance spikes due to GC.
If performance is an issue though, I'd consider other methods of performance tuning than simply increasing the RAM.
I found a few useful documentation on JIRA performance tuning and scaling:
Hope it helps
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs