Re:JIRA is an antipattern
by slider_thor on Sunday December 09, 2018 @09:12PM
(#18644685)
Jira Cloud & Jira Server (on-premise) are two different beasts. I can speak for on-premise only. On my on-premise system which is located on the other coast of the country, a ticket loads in 1.5 ~ 2.5 seconds once your assets are cached at least once by your browser.
Things I've seen that can adversely affect your speed: installing random plugins that are poorly written, integrations, having too many admins over-complicating the Jira configuration.
Learn the keyboard shortcuts to speed up your basic operations.
Re:JIRA is an antipattern
by iainmerrick on Monday December 10, 2018 @03:32AM
(#18646204)
1.5–2.5 seconds is slow. (Faster than I’m getting, though, I’ll give you that.)
Cloud performance is poor. OOTB Server install isn't a silver bullet nor is Data center.
It's a spawling Java app with hundreds of discrete components, aging plugin architecture and is susceptible to configuration creep.
Yeah running it on premise should be faster.
The more fields you configure, the slower it gets.
(That seems to be my impression, at least).
Re:JIRA is an antipattern
by mxschumacher on Sunday December 09, 2018 @03:54PM
(#18643196)
same for me. ~7s load times on a 100 Mbs connection with a new macbook pro are a daily encounter.
It seems to me that it’s slow on a number of levels. It just takes a long time to load each page, and on top of that, basic operations usually take far too many clicks. So I figured it was just a bad tool.