David Hoffman asked this question · 71 karma · Aug 11 '12 at 11:19 AM
I have a Jira 3.13.4 Standalone instance that has approximately 342K issues (in 180 projects) running as a service with a maximum memory setting of 1536MB. It is my understanding that this is the maximum allowed by the 32 bit service wrapper. At this point our installation is essentially useless because it takes anywhere from 2-3 minutes from the time you submit something for write (comment, attribute update, new ticket, etc etc).
We thought that perhaps allocating more memory to the system would increase performance, however any setting about 1536MB fails outright. We even tried starting the tomcat from the command line to see if the memory was indeed the issue. To our chagrin, we can't even go above the 1536MB cap from the command line.
Does anyone have any suggestions (other than upgrading - we are doing this in parrallel but as you can imagine there are tons of customizations that are slowing us down and therefore the likelihood of this succeeding anytime in the immediate future is slim to none)?
Note: We have already pruned about 160K issues (as well as removing obsolete projects). This had NO effect on performance, before OR after reindexing.
I am also open to the fact that I may be barking up the wrong tree... Here are the JVM statistics for my installation. It appears to me that even though it has sucked up 1479MB of RAM that it is only USING 376MB of that.