We use cloud version of Jira and Confluence on South Korea, but it is too slow to the point where we cannot use!
Is it a network issue? or Attlassian server issue? How can I make it fast?
I'm Ivan, a Product Manager from Jira Software Cloud.
I'm working on improving the board and backlog page load times of next-gen projects, while @Tejasvita Madan the PM from Classic is working on the same for board and backlog page load times of Classic projects.
We're also working with many teams across the company to improve load times, such as Jira platform teams working on experiences such as issue view, dashboards, issue navigators, as well as sharing knowledge/insights about performance with the Confluence PM on performance, @Dennis Lu.
We're committed to improving the performance for Jira, as communicated publicly in this roadmap for Atlassian Cloud: https://www.atlassian.com/roadmap/cloud?category=performanceReliability&
We apologize for the issues faced by your teams as you experience slow load times, but we're committed to turn that around in the coming year.
This is especially crucial as our whole company prioritizes performance and scale, while we look to sunset Server products (as per blog https://www.atlassian.com/blog/announcements/journey-to-cloud) to focus on our cloud and data centre products.
Product Manager, Jira Software Cloud
P.S: If you're keen to chat about next-gen performance, please schedule a chat with me: https://calendly.com/iteong/next-gen-performance
Hi everyone, I am the product manager on boards and backlog in classic projects and I am keen to understand performance issues you may be facing with regard to them- please pick a slot on my calendar should you want to chat regarding classic performance:
I've been working with Jira and Confluence at various employers for many years now and it has been almost ubiquitous to expect that it is a painfully slow experience. I find it really difficult to believe, as is suggested above, that the issues are related to individual instances of the application.
On top of that, one of the JS files loaded is JQUERY! Which kinda blows my mind given that it is 2020 and not 2008... Sure lots of Wordpress blogs still use jquery but any serious web application left jquery in the dust years ago in favour of far more modern technologies.
Working with Atlassian products is a constant exercise in frustration and always has been. It is like working in slow motion. If I wasn't forced to use the tools by my employers I would never touch these products again. The ONLY reason tools like Jira are still used is because, as far as I know, there is no real competitor in the space that delivers the same volume of features. The second one pops up, a mass exodus off Jira will begin.
Performance just doesn't seem like it is ever a priority for Atlassian. Hell, I just ran atlassian.com through Google Page Speed insights and it scored an embarrassingly low 14 out of 100 for desktop and an even more despicable 4 out of 100 for mobile.
I really hope that Atlassian is taking a serious look at how archaic their entire platform is because every tool or page I visit with their logo on it is radically slower than any other service that I interact with on a daily basis.
I know Atlassian's motto is "Move Work Forward" but it really should be: "Slow Work Down"
Dear Atlassian team,
This is most definitely not an attempt to compare a proof of concept to a real enterprise grade system like yours.
What I'm trying to say that the modern front-end SPA app can and should be light-weight.
We stumbled about this proof of concept today:
Ivor agreed I could share with you this, obviously with a disclaimer that his project was not intended to be a complete Jira implementation. However - play around with his app, watch the API calls, browser resource usage, see the UX etc.
Maybe it will help you guys with some ideas how to trouble shoot and improve your UI.
And, yes, I know you're not using React :)
Hopefully it helps!
OMG that is so AMAZING I almost CRIED! :'(
I can only DREAM of Jira working this fast.
But Jira is not on top of NodeJS,
Jira does not use reactive libraries,
Jira is... just like godzilla, really... old, ancient, king of monsters..
I can't say how happy it makes me to see that I'm not the only one who can't stand the sluggishness of this system.
I'm so sorry you two are also affected by the slowness in Cloud. We're having a look at instances individually to understand what causes the delay.
Could you please raise a ticket with the Cloud Support Team so we can get a look at your instance and understand what is causing the slowness?
If either of you have trouble doing that, just let me know and I'll take care of that for you.
We ended up migrating from Next-gen projects to Classic projects. I'm not aware of architecture differences between the two project types, but it definitely helped us.
The load time went down from 10-30 (!) seconds to 1-5 seconds. Like I said before, 5 seconds is way too long for a modern web app, but at least it's possible to work with Jira now.
Something to really keep in mind if you decide to migrate, like Daniel Woo mentioned - is the user permission scheme.
I am also frustrated with the painfully slow response time of Jira Cloud. The "golden rule" in web response is 7 seconds. Any response that takes 7 seconds or longer is unacceptable for a web application. Jira cloud is now WAY beyond that and often just hangs. Unacceptable! Jira & Confluence were excellent products that unfortunately have gone downhill fast after the original creators sold out to big US investors.
Same goes for me. I'm based in New York and a task/sub-task can take 10-20 seconds to open.
It's made it impossible to use during meetings - we can't use JIRA during sprint planning because of the slowness. Everyone has to individually submit changes so that nobody dies of old age while we all sit and watch single sub-tasks be added to the backlog together.
Hi everyone, posting here will not change much. Atlassian has public issue tracker where based on votes, they take issues in consideration. As such, I have created a performance improvement ticket:
Please go to that page and put your votes. Thanks 🙏
Hello Atlassian Team,
Jira is super slow for us too. Loading times between 4-20 seconds for every click.
It is extremely annoying to work with that especially when you setup task and change status.
We are currently using the free version but had plans to upgrade to paid plan for 500-1k employees but with the experience of the free version i can't recommend to roll out the software in the company.
I tried to raise a ticket but it seems not possible for free users therefore i give this feedback here.
Using your site i also realised that the loading times for the community it self are also kinda slow compared to other websites, this to me indicates some major design flaws in the web apps developed by altassian.
If i am wrong and there is a way to get more speed i am more than eager to use Jira company wide if it is a pleasureful experience.
@Tiago Scolari We have actually started evaluating other systems. If it's helpful there are paid plugins on top of GitHub. You'd have to sacrifice the history data that's currently in Jira though as there is no feasible solution to migrate the data (unless Microsoft write one soon, which I would do if I were them).
I do hope that Atlassian will listen to this though! Realistically speaking there is no equally flexible and extensive system on the market at the moment.
Dear Atlassian team - your community is quite large and there are more then enough experienced architects, cloud, back-end, front-end. I believe you could leverage that. We would get a faster system and you would get more money. Win-win, no?
Hi Tiago, Rick,
I'm a PM on Confluence Cloud team, and hopefully you'll believe when I say we're definitely working on trying to improve performance (as is the Jira Cloud team).
We know we're very far behind where we need to be for an excellent user experience, but we do have significant efforts in this area.
One thing we could use help with is some specific feedback from users regarding which particular things are the slowest (for example: space overview, pages with a lot of tables, pages with a lot of images, etc). I understand "everything is slow" is possibility, but the more specific the feedback the better chance we have of tracking and improving it.
What a truly riveting tale chap, do tell it again!
We've heard the same excuses going back years, we aren't buying it any more unless I have news of serious management restructuring.
I look forward to the day we can move off your platform which we are working on doing every day
It's not you personally, I was just being cheeky. As with most companies, it's never just ONE person's fault, especially if you are new here. As we are all adults I think we are fairly well experienced with the typical boilerplate responses to these types of issues, whether from Microsoft or Atlassian or any other company.
The issues with Jira, and Atlassian as a whole run deep. The issues are endemic - feature requests for basic functionality have been open for years. I can't be arsed to go get examples but they should not be hard to find.
I wish you and the company success, I really do. But MS365 and other alternatives are looking mighty fine :)
Same here. It feels like sitting behind a dial up modem.
One company I work for hosts itself, that feels like 10 times the speed, and they run more plugins than my cloud instance.
Honestly, performance is total crap. And no, I'm not going to debug that for you, atlassian. Just take a browser, create a project with a simple workflow, create 5 tickets, move them to edit, comment and close. Sequentially.
This should be doable in 2-3 mins. It is far from that.
It could be any number of things. The best thing to do first is to review this article:
Please make sure to follow all troubleshooting steps to narrow down your issue.
Failing that, you can generate a HAR file and review it to see what might be causing the slowness:
Let us know if you have any trouble.
Hi @Pimin Konstantin Kefaloukos, @Shannon Spaniol I see 6-12 second load times consistently. I just get the strong impression Cloud Confluence (or probably JIRA) don't have a viable architecture for performance.
They're doing way too much in front-end JS, with hugely scattered data fetching (650 requests to load a page, of which 100 are over the network).
It all just seems pretty clear to me.
Thank you for following-up on this thread. We'd really love to get more information about the performance issues you are experiencing. It will help us out if you can obtain the troubleshooting information we require per the two articles I sent earlier:
Please send these details to our Confluence Cloud Support Team so we can get to the bottom of this!
If you are on Jira Server instead of Cloud, I would ask that you make sure you have the relevant troubleshooting information from the following article:
Please also include a copy of your HAR file from above. You can then send that to our support team and they can help you out with this.
Thank you for your understanding!
Could you give us some visibility on your current work & roadmap at Atlassian related to having a usable JiRA Cloud experience ? End user performance is the #1 criterion when you use 5hours+ a PM tool.
It's a pity the cloud experience is so bad, as it's supposed the easy way to explore the tool.
You should definitively consider real use cases with people using your tool from Europe, using decent Intel i5 core 2Ghz/4Cores with "only" 8GB" RAM under firefox, and measure yourself the 8s to 10seconds required to display the active sprint or the backlog page.
I have two projects with 15 engineeers and no more than 3000 tickets... It's not what I called "big projects".
Please, do notreply by requesting a support request. JIRA should help me manage my teams, and I don't want to bother to dig more into the reason of this slowness. It's not my job.
I wish you a good day,
I just wanted to add some context that our current metrics show almost all Confluence Cloud requests being delivered to the browser (might take the browser a little more time after that to render the page) in about 3 seconds or less. If you're not getting this experience, follow the articles in Shannon's answer to narrow down the cause and open a case with our support team.
Daniel | Atlassian Support
3 seconds or less? I don't know what standards you have at Atlassian, but now I begin to understand. 3 seconds is clearly too slow. This is the order of magnitude where it's not just a minor performance flaw, it's where productivity is severly affected: https://www.nngroup.com/articles/response-times-3-important-limits/
Could it be optimized so that 90 percent of requests are below 500ms and total uncached page load times to be below 1 second for 90 percent of requests?
There are well know UI/UX standards.
Please do read:
"“…users get impatient and notice that they’re waiting for a slow computer to respond… after about 10 seconds, the average attention span is maxed out."
Please note that end users do not care how fast a request is delivered to the browser. The care about the User Experience as a whole. I wrote in another post that having 3 Jira boards open in any browser will take away from 5 GB to 8 GB of RAM, making the slower hardware unusable.
Also, 3 seconds for a request time is a far cry from what most of AWS services is able deliver (single digit milliseconds, if it's hundreds one should seriously start staring in the general direction of your architect team).
+1 on the opinion that 3 seconds or less to load a site is 600% too long. For comparison, Facebook consistently loads below 1 second. But then again, they actually care about performance (GraphQL, etc.) unlike Atlassian. You need to wake up. Like someone said, if another company emerges with the same set of features, then you're done.
For what it's worth, I ran into the issue where the UI was refreshing very slowly—even populating status lists to update a ticket's status was taking several seconds. Also loading comments and other seemingly quick actions. I went into the developer console and cleared out all localstorage, session storage, cookies, and cache data for our Atlassian Cloud site, then reloaded the page and it's working much better now. YMMV.
Hi @David Aguilera Sure. To get to the console in Chrome:
To open the developerconsolewindow onChrome,usethe keyboard shortcut Ctrl Shift J (on Windows) or Ctrl Option J (onMac). Alternatively, you canusetheChromemenu in thebrowserwindow, select the option "More Tools," and then select "Developer Tools."
From there, there will be some tabs, click on "Application."
In the left pane, you will see Local Storage, Session Storage, and "Cookies." Expand all three.
Right-click on the URL in all three, and choose "Clear."
That should do it after a refresh, but to be safe, log out, clear your browser cache, then quit and relaunch your browser and log in again.
We had Atlassian team help us migrate from Next-Gen projects into Classic projects. There are some issues but we can leave with them as a good trade-off for the speed.
The Classic projects in Jira Cloud are as fast as our old Jira Server on-prem. We have response times of 1-4 seconds on average. It's not super-fast but we can at least work with it.
If the performance issue is related to Next-gen board as @Rick Zakharov stated above, it's also important to keep in mind that Next-gen projects behave differently than Classic projects in terms of permissions, notifications and anything that has the concept of scheme.
In this documentation it states that:
Which takes us to a page that contains a diagram that explains how these permissions work for example.
If you have a business requirement that only allows certain groups of users to have access to particular projects, it might be a good idea to, after creating the classic projects to migrate to, consider creating separate permission schemes to each project, configuring each of them according to each project's requirement.
Summarizing it: keep in mind that Next-gen and Classic work differently in terms of how to configure permissions.
Daniel Woo | Atlassian Cloud Support
Like the others, all the tools except trello are definitly slow to the point it became unusable because it's frustrating compared to most of the web apps out there. We migrated our wiki to Confluence and now I regret it, because day to day, it's a pain to deal with.
Also, seeing that EVERYONE had issues for years even prior to this question and it still hasn't improved is definitely not a good sign. It doesn't seem like something that can be solved.
Opening a ticket to the cloud support team won't help, as it's not related to a single use-case, it's the whole platform!
We'll move in a few weeks but definitely not happy about it, we enjoy the features from both Jira and Confluence and it's always time consuming to move
Jira needs so much processing power from my laptop (MacBook Pro late 2013). In the next Apple keynote event they will probably start using Jira as one of the benchmarks: "Jira issues open 2.5 times faster" 😃. I'm hoping the new MacBook with M1 will be able to open these issues faster.
After being a happy confluence user / consultant for more than 10 years now I am looking for ways to become less dependent from a single provider. One idea is to move all structured data from confluence into a postgres database via the fantastic PlaySQL Plugin. Anybody interested in discussing strategy just pm me.
- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events