Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to make JIRA faster?

Are there any simple tips on how to make the default JIRA installation faster and more responsive? We use MS SQL Server as a backend.

I know JIRA is a big piece of software and that kind of justifies slower page loads but still, if there are some simple tips on how to improve JIRA's performance, I'd like to try them.

3 answers

1 accepted

Jamie beat me to what I'd post, but I'd also add "use a proper browser" as a client side improvement. That pretty much means "not Internet Explorer" to most users.

Like Christopher_Chalmers likes this

Totally agree, with the tacit understanding that that's not always possible ;-)

JIRA is slow for us even in Chrome, I guess it doesn't have anything to do with the client side in our case.

Will read through the documentation, thanks.

Like # people like this

I'd ask a separate question with specifics... eg what screens, what plugins, how many issues. If you have experience inhouse try load-testing and profiling... http://blogs.onresolve.com/?p=95 plus loads of info on this subject elsewhere.

It is not always an internet explorer problem guys. Open you mind a bit more. JIRA is slow. Nothing to do with browser.

Like # people like this

Jamie's original answer covers that comment.  It can be a range of things.  One of the possibilities is the browser.  As we've proved it's the browser in several cases (and IE is by far the largest culprit of bad browser behaviour).

We have a large issue / project base. Here is some generic tips i can share

  1. We used Oracle DB as we had inhouse expertise, its a deicated schema on a seperate machine with very good hardware
  2. Provided enough resources for our VM (hardware and memory) where JIRA runs and its a dedicated ESX for the Atlassian Products (JIRA/Confluence)
  3. Indexing is on a seperate drive altogether (fast access disc), helps a lot
  4. Add plugins carefully, some plugins are killers ....
  5. No N/W hops between the DB and production machine
  6. GZIP Compression enabled

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

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

Events near you