3 ms·

Ours JIRA instance took multiple seconds to load modals. Think 5+ seconds. It was miserable. I would have gladly paid more for faster speed but it turned out t

by tbrock 6y ago

Ours JIRA instance took multiple seconds to load modals. Think 5+ seconds. It was miserable. I would have gladly paid more for faster speed but it turned out the APIs were blazing fast and it was the JS that was slow. Not sure how we have had such different experiences. Seems impossible that your JS was executed that much faster than mine. I was using chrome FWIW.

CraigJPerry 6y ago
5+ seconds sounds wild. Our active users number is a multiple of the 5k max users for jira cloud and the only actions i can think of that are >2s are bulk edits and complex jql
- tbrock 6y ago
  We must have been using it incorrectly then, oh well. Good riddance Atlassian.
  - hinkley 6y ago
    Almost everyone is “using it incorrectly”, but it’s like the aphorism about assholes. (If you meet assholes all day long, you’re the asshole.) If your software encounters idiots all day long, you’re the idiot.
dathinab 6y ago
Might be a problem with customization. THE main problem with JIRA is people breaking it with customization in one way or another. Or put is on very slow, high network latency servers... EDIT: Just to be clear, JIRA is never fast. But can be usable if you are not super sensitive to small latency.
- hinkley 6y ago
  The main problem with Windows 95 stability was garbage third party drivers, but we had no problem blaming Microsoft for that. Really, why wouldn’t you blame the maker of the bed? If you make a tool that encourages Rube Goldberg machines, then you made something far worse than a Rube Goldberg machine; you built a device to construct them.
- nicoburns 6y ago
  > But can be usable if you are not super sensitive to small latency. Our JIRA instance would lag while typing in the description box. You have to wait a second or two for it to catch up after typing a sentence. It was absolutely unusable.
qzio 6y ago
I actually got $work to pay for a new desktop computer to prevent me from going insane because of the slugish JIRA and Google Cloud Web Console, and it actually solved it. My old x260 was not able to run jira/gcp/slack at a reasonable speed due to javascript performance :(

by tbrock 6y ago

CraigJPerry 6y ago

5+ seconds sounds wild. Our active users number is a multiple of the 5k max users for jira cloud and the only actions i can think of that are >2s are bulk edits and complex jql

tbrock 6y ago
We must have been using it incorrectly then, oh well. Good riddance Atlassian.
- hinkley 6y ago
  Almost everyone is “using it incorrectly”, but it’s like the aphorism about assholes. (If you meet assholes all day long, you’re the asshole.) If your software encounters idiots all day long, you’re the idiot.

dathinab 6y ago

Might be a problem with customization. THE main problem with JIRA is people breaking it with customization in one way or another. Or put is on very slow, high network latency servers... EDIT: Just to be clear, JIRA is never fast. But can be usable if you are not super sensitive to small latency.

hinkley 6y ago
The main problem with Windows 95 stability was garbage third party drivers, but we had no problem blaming Microsoft for that. Really, why wouldn’t you blame the maker of the bed? If you make a tool that encourages Rube Goldberg machines, then you made something far worse than a Rube Goldberg machine; you built a device to construct them.
nicoburns 6y ago
> But can be usable if you are not super sensitive to small latency. Our JIRA instance would lag while typing in the description box. You have to wait a second or two for it to catch up after typing a sentence. It was absolutely unusable.

qzio 6y ago

I actually got $work to pay for a new desktop computer to prevent me from going insane because of the slugish JIRA and Google Cloud Web Console, and it actually solved it. My old x260 was not able to run jira/gcp/slack at a reasonable speed due to javascript performance :(