3 ms·
I used it (Jira) for a short period of time a while back. I seem to recall that it's performance was highly influenced by non-obvious JVM parameters, and bits o
by ineedasername 7y ago
I used it (Jira) for a short period of time a while back. I seem to recall that it's performance was highly influenced by non-obvious JVM parameters, and bits of the system would stall or crash without a clear pattern until a bit of trial & error with parameters solved it. It wasn't very "turn key" and the out-of-the-box config were... less than ideal. This was for a single user (me) so it's not like there was a much of a resource crunch.
- jakemal 7y agoMost pages take 10+ seconds to load for us and we are using Atlassian's hosting.
- user1980 7y agoOpening up the Network Inspector when loading a single issue in the "new" UI shows a dumpster fire of 128 requests, 5 MB transferred. It's like the paradox of the heap: No one request is abnormally slow (although a 1.1MB slug of unminified JS from jiraplugin.zendesk.com sure isn't helping things) but the whole thing combines to give JIRA a reputation it surely deserves.