We are having an issue where Jira is very slow/unresponsive during a specific time-frame every day. During this slow-down time, creating, updating, and commenting tickets take a full minute. Loading between pages or projects is either very slow or throws "Internal Error Occurred" errors. This is a Windows 2016 VM on vCenter and it has 12vcpu and 32GB RAM on a Performance disk. We have increased the JVM RAM as well. When we do a disk access speed test, they are very high during non-peak hours.
We have ruled out automated backups, antivirus, and contention with other applications on the same VM. Anyone have ideas besides moving to Linux?
I have seen this on windows machines caused by many different things. I would like you to answer a couple of things for me.
Look forward to getting additional information back.
Great so we know that the CPU is the issue if it is tapped when you are having the slowness. The CPU only has so many threads to process information on. The CPU is serving both the server and DB which could be the issue, you might not be sized correctly. Couple more questions.
In regards to DB threads and DB threads in Jira it is how many connections you are allowing. This can be an issue if there are not enough of them. https://confluence.atlassian.com/adminjiraserver/tuning-database-connections-938846864.html The information you provide above will help determine the issue.
60% is actually acceptable on RAM. Sounds like the processor is working a bit hard, Is it at 60% all the time or does it spike up higher during slowness? The DB actually looks healthy and is not taking a hit so that is not the issue. Is the CPU dedicated on the VM or is it shared? If it is shared then other VMs on the stake could be affecting your application.
I would recommend reserving the minimum that is required for your Jira instance size https://confluence.atlassian.com/jirakb/jira-server-sizing-guide-975033809.html
I have seen slow down on Jira VM instances when the shares are used by other VMs during load when reserves are not in place. Give that a try and see if that fixes the issue. You should be able to look at the VM logs and see if the slowness correlated to CPU usage by other VMs.
Hi everyone - in case you haven’t heard, we’re hosting the show of the century on November 10th: High Velocity: ITSM World Tour. This virtual, concert-themed experience...
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