[adkadskhj]

I could agree with you from a UX-flow perspective, but the tech is so shoddy that i loathe it. Everything is a "web 2.0" monstrosity of load times and popin. Open the wrong link and it takes you 40 seconds for components to popin, pull data, render, move to the highlighted component, it to popin, pull data, render, and finally you get what you want.

The UX-flow might be good, not sure, but the tech is so bad it actually inhibits users. The use of independent components might be neat when loading a Jira card from Bitbucket pull requests (which works), but it makes loading Jira cards from... Jira, terrible. Imo.

[user5994461]

>>> Open the wrong link and it takes you 40 seconds

There's nothing in JIRA that take anywhere near 40 seconds to open.

If you really have pages that take double digit seconds to open (you can open your browser's development tools to measure), it's more likely administrator in your company that is to blame for doing a horrible setup running the web service on a toaster and the database on a NAS.

[adkadskhj]

You're right, i'm sensitive to load times and exaggerated by approximately 4x.

I just (loosely) timed it, it took ~10-12s to open a backlog selected issue card _with cache_ from refresh. I used that example because it highlights the list i gave before.

1. The page loads, a bit slow in general.

2. The dom has loaded, so now backlog issues are loading.

3. The backlog issues are loaded, so now the selected component opens.

4. The selected issue component starts loading data.

5. Your data is now finally visible.

The ~10-12s is loosely evenly spread through the entire steps 1-5. This is on Jira Cloud, no "toaster NAS" unless you want to blame Jira Cloud for running a toaster, in which case i'd agree.

The problem in my mind isn't the servers. Opening the network tab, you see requests responding a bit slow, maybe 50-500ms, but not _terrible_. I'd like to see all requests below 300ms personally.

The problem is the UI design. Everything executes dynamically and sequentially. The URL indicates exactly what sort of page i want to see, but nothing is loaded until the JS loads, renders, makes a request for whatever data that individual component needs. Any sub-components to this then get rinse and repeat once they are actually loaded.

When you stack components on components on components that all need to sequentially load data a 1-2s load time starts to stack up, fast. And best of all, network requests are slowed down by how fast your DOM renders? Ugh.

[sofixa]

What's the excuse for Jira Cloud? It sometimes takes up to 60s to open a popup window with an issue's details.

[hn_throwaway_99]

I am so curious as to what setup causes these horrific load times. I never, never have performance issues like these with Jira Cloud. A "slow" load for me is about 4 seconds, normally cards open in a second or two.

[adkadskhj]

I gave an example here: https://news.ycombinator.com/item?id=27909949

But in addition to that, 1-3 seconds per click is horrible imo. I have to literally pause, and slow down my workflow, because every input (navigation click) takes 1-3 seconds to load? That sort of delay starts to drag on users, imo.

Wasn't JS based UI's supposed to _lighten_ the load? Make web pages faster because they could just ask for the data that changed? This feels like such a massive step backward from simple HTML, like HN.

1-3 seconds being good, or even okay, is abysmal to me. Especially when the full page isn't needed, just a handful of data. Something is fundamentally broken with this version of the "modern web". And i say that as a web developer who loves complex frontend technologies. But to me if the user isn't getting a faster response, the frontend tech would be better off as plain HTML.

[ralgozino]

I used to manage an on-prem Jira installation at $OLD_JOB, the amount of network traffic that the page to view an issue does is absurd. If you have a speedy connection or most of the page cached you won't notice, but switch to slower connections or a congested enterprise VPN and it's painfully slow. Open the browser's toolbox, disable the cache and reload. See for yourself.

[jgalentine007]

We've had performance issues with cloud Jira / Bitbucket the last couple months. Doing simple merges can take 2 minutes in the background. I encounter 5-10 second slow downs multiple times a week with other parts of the UI. GitHub is instantaneous in comparison.