I have just installed JIRA on my server. It successfully installed, however, when I tried to bring up JIRA from the Windows start menu it is extremely slow!
Has anyone encountered similar problem?
There's all sorts of reasons it could be "slow", but as it's a new installation, it's quite likely that...
With an empty Jira, we can rule out dodgy configuration, users thrashing it, too much data, etc. Start with the virus checker - if you have one, turn it off and see if things improve. If it's not that, then look at the resources - how much memory have you given Jira? Monitor memory and CPU usage while it's starting up.
Nuon, please also refer to the following link:https://confluence.atlassian.com/display/JIRAKB/Crashes+and+Performance+Issues+Troubleshooting
It is indeed very very slow in Firefox. It just stalls on many actions.
The product is just slow, I have it hosted with atlassian and frequently experience 5-12 seconds response times for pages to load. At this point I want to drop JIRA and use something else, anything else.
Yea, I'm experiencing the same thing. 5-12 seconds. A shame, seems like exactly what we need too.
There are two things here. 1. Some users experience massive performance issues with Cloud JIRA, despite having decent network connectivity. Atlassian don't seem to be doing anything to fix this, so those users need to consider hosting it with someone who will fix it (check the partner/expert list) or hosting it themselves where they can deal with whatever the issue is here. 2. If your server is running slow, you've either underpowered it, misconfigured it, or overloaded it. That's something you need to look into yourself. Telling us "it's slow" is not much use, you need to tell us what you've done that makes it slow.
Haha, i recently updated sourcetree, after which it stopped even committing files, and the ui designs sucks (im ui designer haha) and i raged a bit, went to their official JIRA tracker for sourctree and...
It crashed firefox ! hahaha So bad!
Because it's not slow for most of them, and doesn't crash standard browsers?"How do they have so many customers" is an excellent question - if everyone were having the problems you are having, then they would have lost them. Their customers obviously don't have these issues, so the question becomes "what are you doing differently to the users who are not having problems?"(As for Sourcetree though - the latest release is pretty much reviled by everyone - they got that wrong)
I dont know and i don't care. I use sourcetree version 1.5.2 (yeah that old) because it was the last reliable build without ANY problems whatsoever, after that everything went downhill for me, starting from ui glitches, lags, freezes on scanning directories etc.
Honestly the best part of sourcetree is ui, and with 1.5.2 stability its perfect for me and my peeps,
as of to ALL OTHER products they just.. poor. Design is dry and poor, everything is slow and unresponsive. Ui of web based sucks big time, if you ask me. I look at github and they just get it, the designers at Atlassian just can't into. they just don't get it, i dunno. Im really happy i didn't make the decision to stay with them, and a year ago i was hesitating to what platform to use, and gh is by far superior imo.
i know man for this exact reason my first meeting with JIRA took roughly 10 minutes, 9 of which i waited different pages to load. first and last.
Just stating "JIRA is slow" will not make any babies. I agree that sometimes the instances support.atlassian.com, jira.atlassian.com and so forth are a bit slow, and i wish Atlassian would eat some more of it's own dogfood and show us the value of a datacenter license with enough nodes to make it smooth sailing, and at the same time save their customers from "Go get yourself a snack"-errors during their "planned" outages.
Back to the issue in the question:
Nuon MAO-Phumarun: Stating "JIRA is slow" is like saying "the string is too long". Act like a system admin and figure out what causes it.
How? If you are a firefox user there is a great plugin called Firebug. Install it, activate it and surf to you instance and start looking into where time is wasted. JIRA is notoriously chatty, so what seems like a simple "load a dashboard" is actually a frameset sent over, a java scripts that sends some client side data back to the server, a possible response-time to returns data, and this goes on and on until all elements of the page is loaded.
A simple server configuration error like a dead DNS which gets round-robin'ed in on every 3rd request, can cause minutes of wait on a page that bounces data back and forward 40 times.
Pay attention to what Nic stated as well about server having to little resources handed to it. A plugin like Java Melody can give great insight in which java memory configs that might become exhausted, what actions that causes the server CPU to peak.
It looks like you're new here. Sign in or register to get started.
![Photo of Sharath AV [YML]](https://us.v-cdn.net/6038660/uploads/avatars/32/c0/n32c037263a405bcd7ad7b99421d8049f.png)
