Peformance Issue - JIRA /Windows Server 2012 R2/ Tomcat

[Mark Gordon]

Team,

We are evaluating JIRA. We are using an Amazon VM with Windows Server 2012 R2 and Tomcat.

We have 2 cpu and 4 gig on vm Amazone setup.

We are having some serious performance problems. When the browser launches with just one person, it is sluggish. Once we get the screen back on the dashboard, we can go to other things such as project/administration. Then, the browswer will hang so badly that we have to kill it.

Using task manager, there are no ram issues but the CPU goes to 100% during these poor performance events. The process causing this appears to be TomCat. Again, there are no RAM issues that we can see. Are they are suggestions on this from anyone?

Thanks

[Nic Brough -Adaptavist-]

The usual culprit on a windows box is a virus scanner, and the second one is usually "inadequate allocation of resources" (not enough memory for the JVM for example, or putting the data directory on a SAN based disk instead of local storage) but it could be all sorts of other things.

Have a scan through https://confluence.atlassian.com/display/JIRAKB/JIRA+Performance+Tuningfor some hints over the "virus scanner" comment

[Mark Gordon]

Nic, Thanks again for those thoughts. I will review the link. We know it is not memory. We can watch the browser start to choke, opening task manager, see CPU go to 100% and stay there for a very long time, memory is stil way below any concern. With that, any other things you have run into that cause this?

[Nic Brough -Adaptavist-]

What monitoring are you doing inside the JVM to make you think it's not the memory?

[Mark Gordon]

Nic, good point. We have been using Task Manager on the Actual VM server itself. Is there a reason why task manager would not report this correctly being we are ON the server?

[Nic Brough -Adaptavist-]

JVM memory handling is a lot more complex than "the OS says I'm using this much", you've got garbage collection, permanent generation, eden memory and all the rest going on. Memory issues can cause CPU if it's trying to do garbage collection too much for example.

Start with the basics - how much memory have you allocated?

[Mark Gordon]

Nic, We have 4 gig of memory allocated on the VM instance.

[Nic Brough -Adaptavist-]

Sorry, I meant allocated to Tomcat/Jira. You might have 4Gb on the machine, but if you've only given Jira 256Mb, it's really going to crawl and thrash the CPU

[Mark Gordon]

Nic,

We finally got it working. It was an issue with making sure it was using the memory we setup. appparently it was tied to how we start it. https://confluence.atlassian.com/display/JIRA/Increasing+JIRA+Memory#IncreasingJIRAMemory-guidance

Thanks again.