News for hackers. Stuff that matters.

A comment on Atlassian to shed 5 per cent of workers. Parent comment

Re:Atlassian to shed 5 per cent of workers by climb_stealth on Tuesday March 07, 2023 @02:05AM (#35052466)
I wonder if self-hosting is the performance difference. I have worked in projects with 15 years of history in Jira. And they were fine. It feels kind of slow but in reality it takes maybe three seconds to load any ticket.

But actual minutes to load stuff? That is insane and I can see where the loathing would come from.

[ Parent | on HN ]
Re:Atlassian to shed 5 per cent of workers by esperent on Tuesday March 07, 2023 @02:35AM (#35052625)
* * *
[ Parent | on HN ]
Re:Atlassian to shed 5 per cent of workers by doctor_eval on Tuesday March 07, 2023 @08:01AM (#35054826)
A ten second load time is about 100x worse than it should be.

Exaggerating it to several minutes is less egregious by an order of magnitude.

[ Parent | on HN ]
Re:Atlassian to shed 5 per cent of workers by AlotOfReading on Tuesday March 07, 2023 @10:49AM (#35056681)
I measured that extreme load time with a stopwatch and the debug console, but it was admittedly under abnormal circumstances. Not sure I'd notice 10s TTI enough to complain. That's a pretty normal number these days.
[ Parent | on HN ]
Re:Atlassian to shed 5 per cent of workers by re-thc on Tuesday March 07, 2023 @06:28AM (#35054156)
A lot of anecdotes are possibly from some years ago where self-hosting JIRA meant a single server on-premise. You might not get a lot of resources and can be used by the entire organization. The server would be at or over capacity 90% of the time so things could take forever to load.

Self-hosted JIRA also opened up to lots of customisations and hacks, which often weren't performant.

[ Parent | on HN ]
Re:Atlassian to shed 5 per cent of workers by jamesfinlayson on Tuesday March 07, 2023 @08:09PM (#35063835)
With enough data it's possible - I remember a colleague going to a conference and chatting with some Atlassian people and they said their priority (this was probably 2016 or 2017) was getting Jira to be performant for companies with 500,000+ people. With enough users, labels, releases etc I can see Jira churning on something for minutes.
[ Parent | on HN ]