JIRA appears to be experiencing performance issues and is running slowly. This will be particularly noticeable in the following areas:
- The Issue Navigator
- Opening Issues
Disk access speed is critical for JIRA performance, particularly due to the heavy use of disk I/O as indexes are read each time a search is made and written each time an update to an issue is committed. We have a KB article on Searching, Indexing, and Filters Troubleshooting which contains further information on this.
If JIRA or Confluence are running slowly, disk speed can be a potential root cause. It's possible to isolate that cause using this Support Tools Utility to benchmark the disk access speed.
This basic test will perform the open, read/write, close and delete operations 1000 times to a temporary file in the
java.io.tmpdir directory for each measurement, reporting the results as in the assessment section below. This test is the closest we can get to simulating the performance of a Java process when it comes to accessing the file system, allowing it to be an accurate measurement for JIRA's performance when utilising the disk. Other disk measurement tools may provide different results if they do not measure the specific performance of the Java JDK/JRE.
The Java source can be found within the JAR - if the file is uncompressed it can be viewed.
When reviewing the benchmark results:
- Focus primarily on the average result.
- When the open & close speeds are bad and the r/w is good, the likely cause is anti-virus.
- Open and close are important values as JIRA will access the indexes very often - the average search will close a file many times.
- A high minimum and average speed may be indicative of a low speed disk or hardware fault.
- If a disk has a high average and low minimum speed, there may be an environmental factor at play (see below for further information).
Grading the Results
Below is a breakdown of approximate average speeds that can be used to grade the results.
|Open||< 40,000||< 80,000||> 150,000|
|Read/Write||< 40,000||< 60,000||> 100,000|
|Close||< 20,000||< 40,000||> 100,000|
|Delete||< 50,000||< 200,000||> 300,000|
Examples of environmental factors that can cause slow disk access are as follows:
- Anti-Virus software. As in our Crashes and Performance Issues Troubleshooting KB article, Anti-Virus software can be detrimental to the operation of JIRA as it will limit open and close times.
- A remote disk or shared drive.
- Synchronisation to another machine over a slow network.
- A virtualised OS, such as VMWare (see Virtualizing JIRA (JIRA on VMware) for further information).
- A disk defragment job may be running.
- Hardware issues such as disk failure.
- File system encryption.
- Automated compression of files controlled by the OS.
- Specific issues with the Java version and OS. This is rare occurrence, however a bug or known issue within the JVM may cause it to perform poorly on a specific OS.
- Other applications or operations that are currently using the disk.
- The disk capacity may be nearing full, which on some OS can slow the performance of the disk (in this particular example, it was on Solaris).
We have included some sample benchmarks below.
This is a premier hosting provider using disk hardware technology equivalent to a SSD.
This benchmark is of very fast disk with a virus scanner enabled.
This is a WD Black 3.0GB/s 7.2k RPM drive running 5 JIRA instances during low load (whilst we would not ever recommend to do this, it does highlight the impact of multiple applications running on the same server).