We have a 2000 user JIRA instance and we are having performance problems every day we need to restart the system to make the application work. the server cpu is 99% at the time JIRA is hanging up. we have dual 2.13 cpu and 6GB ram. So how do we resolve this ? what are log files i need to check for performance problem and do we need to increase heap size in JVM ?
Try to analise atlassian-jira.log. If if have memory troubles you will find record like OutOfMemoryExeption. Also try to analise this log via Hercules (see this:https://marketplace.atlassian.com/plugins/com.atlassian.support.stp/cloud/overview). This addon don need an instalation, just follow to instrctions.
You should review the content on https://confluence.atlassian.com/display/JIRAKB/Troubleshooting+Performance+Problems if you have not already done so and see if that provides any more clues.
Looking at your memory graph it looks like your JVM is still configured with the default settings and so you should also review https://confluence.atlassian.com/jira/increasing-jira-memory-5896.html or the equivalent page for the version of JIRA that you have installed.
Hope this helps
It does no harm to set them the same, although this will mean that your instance will start at its maximum size and remain at that size. If the server on which this is installed is dedicated to hosting JIRA then there should be no other need for any changes of size during operation. Have you reviewed all the steps on the troubleshooting webpage and confirmed it is definitely a memory issue? You may also like to review https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html which gives indications of the suggested sizes of various settings for different size JIRA installs. From the limited information you have provided it seems like your system is probably a Large-scale instance and so you should be looking at least 16GB of system memory with at least 4GB of it allocated to the JVM Heap.
But in this link https://confluence.atlassian.com/display/CONFKB/How+to+fix+out+of+memory+errors+by+increasing+available+memory in Step1 described "Consider setting Xms and Xmx to the same value, as this can decrease the time GC takes to occur, as it will not attempt to resize the heap down on each collection." what is this ?
GC is Garbage Collection the process of recovering used memory that can be recovered to free memory. When used memory is recovered it can take some time to execute and if the memory is too small this will happen frequently leading to performance issues. Have you isolated the issue to be memory related using https://confluence.atlassian.com/display/JIRAKB/Troubleshooting+Performance+Problems? If so please help us to help you by providing the symptoms you observed including a summary of your Garbage Collection logs and your current JVM settings.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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