3 ms·
Do you have ~100 developers using it and 1000s of issues? Definitely does not scale.
by davidu 15y ago
Do you have ~100 developers using it and 1000s of issues? Definitely does not scale.
- nl 15y agoThat's nonsense. I've used it on projects much (MUCH!) bigger than that. You didn't try and use it with the built in database or something did you? For a public example, https://issues.apache.org https://issues.apache.org currently has 209560 issues, thousands of users and it works fine.
- pointyhat 15y ago...until you plug Greenhopper in.
- ghshephard 15y ago919 Active Developers, 118,460 Issues. MySQL Backend. #1 rule of Jira is make sure you have enough memory to keep the mySql Database in cache. The attachments don't matter so much. What I love about the (Lucene?) index is that I can still do a free text search of all 118,000 issues in under 1 second, the same as I was able to when there were only 100 issues. Plus, the 4.x JQL (kind of a simplified Sql Variant) makes it easy to do ludicrously complex searches that still return in basically O(1) time. DavidU - tell me a bit more about your trouble with Jira Scaling - was it case of the backend system not having enough memory? Jira isn't really disk speed limited, so that's about the only thing that could cause you problems. Did you get a chance to run the typical performance tools to see if you were CPU, IO, or Memory Bound?