onresolve team blog

Over the last few months JIRA performance has tanked, but gradually. Difficult to think of any particular inflexion point, just more users, projects and issues.

I had a number of changes I had in mind to help:

• Application server
• DBMS type and location
• Caching for static content
• Reducing numbers of projects, groups etc.
• Optimising indexes.
• Turn gzip compression on.
• Memory and garbage collector settings.
• Bypassing the apache reverse proxy and going direct to Tomcat
• Use AJP13 connector instead of (as well as?) ProxyPass.

BTW, if you're looking for the instruction on where the "go-faster switch" is and can't be bothered to read the following, I'll tell you simply that you should replace the group jira-users in your roles or permission schemes with Anyone. If you're not using that then hopefully there will be something else of interest here, if only how to set up a simple load test to get some figures.

For the record our numbers at the time of testing are:

Issues 112897   Projects 475   Custom Fields 505   Workflows 239   Users 7613   Groups 698

Continue reading ‘How to make JIRA 6 1/2 times faster’