4 ms·
I've never seen JIRA be "pretty fast", so I can't agree. I also think "2000 different fields" is an unfair exaggeration, if we're going to focus on being fair.
by coder543 8y ago
I've never seen JIRA be "pretty fast", so I can't agree. I also think "2000 different fields" is an unfair exaggeration, if we're going to focus on being fair. The 10 to 20 fields that people might use per issue should not prevent JIRA from being fast with the right architecture.
- viraptor 8y agoSame. JIRA is just slow, even in basic configuration. Which is always annoying me because JIRA is 99% read-only. They could generate most of the pages and cache them until anything changes. Even pre-generate then on change. But every time you view an issue, it takes multiple seconds again.
- WrtCdEvrydy 8y agoThis is a common 'but sometimes' issue in software engineering. Caching works for 99.9% of cases, 'but sometimes', I click on an issue and it was just updated just before my page rendered.
- p2detar 8y agoI've setup Jira (on premise) at my workplace myself. Runs behind an nginx reverse proxy and it is indeed pretty fast! We don't use much stuff and it's a bit older version 7.8, but I cannot complain so far.
- Aeolun 8y agoInstalled a plain Jira software instance on Docker, that wasn’t terribly slow.