Re:Treating performance as a product: The technical story of...
by ugh123 on Tuesday August 29, 2017 @04:31PM
(#15127373)
Thats probably dependent on the hardware and size and complexity of workflows and DB size. Our JIRA install is one of the slowest webapps i've seen in a while. Can't wait to move on to something else.
Re:Treating performance as a product: The technical story of...
by morj239 on Tuesday August 29, 2017 @04:53PM
(#15127516)
Would you mind sharing the approximate number of issues and active users in your JIRA install?
Re:Treating performance as a product: The technical story of...
by dasil003 on Tuesday August 29, 2017 @10:20PM
(#15129268)
It varies widely. We have ~300 users, 30 projects, probably on the order of ~20k tickets. Performance has been up and down, occasionally things slow way down and we have to file a ticket and then they come back with some excuse about re-indexing or relocating the instance. Normally it's pretty acceptable, but it feels like there are a ton of a variables that go into its performance day-to-day and minute-to-minute.
Re:Treating performance as a product: The technical story of...
by ugh123 on Tuesday August 29, 2017 @07:59PM
(#15128644)
I'm at a medium/large company, but without access to real numbers i'd say off the top of my head its probably >500 users across 100+ projects and 10s of thousands of issues.
Re:Treating performance as a product: The technical story of...
by veidr on Wednesday August 30, 2017 @02:37AM
(#15130104)
That seems bananas to me, because JIRA is literally the most painfully slow application I've ever used in my entire career. We use their hosted version, though.
Do you host your own JIRA instance and have somebody in charge of running/tweaking it?
Re:Treating performance as a product: The technical story of...
by anotherbrownguy on Wednesday August 30, 2017 @11:08AM
(#15132735)
I have used JIRA only many years ago so I can't compare performance with current Asana. When you say JIRA is slow, is it in comparison with Asana?
Re:Treating performance as a product: The technical story of...
by azinman2 on Tuesday August 29, 2017 @05:37PM
(#15127801)
For me the slowness of JIRA means I loathe going into it. It feels soooo clunky, so 90s in performance and UX. I’m moving to JIRA from trello and it’s night and day. Even something as basic as having a notification inbox with read markers is a paid plugin for JIRA, and everything else seems to require many many clicks (each with their own several second load time). It’s horrible.
I am happy that I can click a JIRA link and see a page within a second.