Performance and scale testing
With every JIRA release, we’re publishing a performance and scaling report that compares performance of the current JIRA version with the previous one. The report also contains results of how various data dimensions (number of custom fields, issues, projects, and so on) affect JIRA, so you can check which of these data dimensions should be limited to have best results when scaling JIRA.
This report is for JIRA 7.9. If you’re looking for other reports, select your version at the top-right.
When some JIRA administrators think about how to scale JIRA, they often focus on the number of issues a single JIRA instance can hold. However, the number of issues is not the only factor that determines the scale of a JIRA instance. To understand how a large instance may perform, you need to consider multiple factors.
This page explains how JIRA performs across different versions and configurations. So whether you are a new JIRA evaluator that wants to understand how JIRA can scale to your growing needs or you're a seasoned JIRA administrator that is interested in taking JIRA to the next level, this page is here to help.
There are two main approaches, which can be used in combination to scale JIRA across your entire organization:
- Scale a single JIRA instance.
- Use JIRA Data Center which provides JIRA clustering.
Here we'll explore techniques to get the most out of JIRA that are common to both approaches. For additional information on JIRA Data Center and how it can improve performance under concurrent load, please refer to our JIRA Data Center page.
Determining the scale of a single JIRA instance
There are multiple factors that may affect JIRA's performance in your organization. These factors fall into the following categories (in no particular order):
- Data size
- The number of issues, comments, and attachments.
- The number of projects.
- The number of JIRA project attributes, such as custom fields, issue types, and schemes.
- The number of users registered in JIRA and groups.
- The number of boards, and the number of issues on the board (when you're using JIRA Software).
- Usage patterns
- The number of users concurrently using JIRA.
- The number of concurrent operations.
- The volume of email notifications.
- The number of plugins (some of which may have their own memory requirements).
- The number of workflow step executions (such as Transitions and Post Functions).
- The number of jobs and scheduled services.
- Deployment environment
- JIRA version used.
- The server JIRA runs on.
- The database used and connectivity to the database.
- The operating system, including its file system.
- JVM configuration.
This page will show how the speed of JIRA can be influenced by the size and characteristics of data stored in the database.
JIRA 7.9 performance
JIRA 7.9 was not focused solely on performance, however we do aim to provide the same, if not better, performance with each release. In this section, we'll compare JIRA 7.9 to JIRA 7.7. We ran the same extensive test scenario for both JIRA versions. The only difference between the scenarios was the JIRA version.
The following chart presents mean response times of individual actions performed in JIRA. To check the details of these actions and the JIRA instance they were performed in, see Testing methodology.
Response times for JIRA actions
Each row represents mean response times. The lower the value, the better the performance.
In JIRA 7.9, the boards’ performance has improved by nearly 30%. That’s because of a fixed bug that affected boards with many epics. Learn more
The following sections detail the testing environment, including hardware specification, and methodology we used in our performance tests.
Before we started the test, we needed to determine what size and shape of data set represents a typical large JIRA instance.
In order to achieve that, we used our Analytics data to form a picture of our customers' environments and what difficulties they face when scaling JIRA in a large organization.
Baseline JIRA data set
|JIRA data dimension||Value|
We chose a mix of actions that would represent a sample of the most common user actions. An "action" in this context is a complete user operation like opening of an Issue in the browser window. The following table details the actions that we included in the script for our testing persona, indicating how many times each action is repeated during a single test run.
|Action name||Description||Number of times an action is performed during a single test run|
|View Dashboard||Opening the Dashboard page.||10|
|Create Issue||Submitting a Create Issue dialog.||5|
|View Issue||Opening an individual issue in a separate browser window.||55|
|Edit Issue||Editing the Summary, Description and other fields of an existing Issue.||5|
|Add Comment||Adding a Comment to an Issue.||2|
|Search with JQL||
Performing a search query using JQL in the Issue Navigator interface.
The following JQL queries were used...
Half of these queries are very heavyweight, which explains high average response time.
|View Board||Opening of Agile Board||10|
|Browse Projects||Opening of the list of Projects (available under Projects > View All Projects menu)||5|
|Browse Boards||Opening of the list of Agile Boards (available under Agile > Manage Boards menu)||2|
|All Actions||A mean of all actions performed during a single test run.||-|
The performance tests were all run on a set of AWS EC2 instances, deployed in the
eu-central-1 region. For each test, the entire environment was reset and rebuilt, and then each test started with some idle cycles to warm up instance caches. Below, you can check the details of the environments used for JIRA Server and JIRA Data Center, as well as the specifications of the EC2 instances.
To run the tests, we used 10 scripted browsers and measured the time taken to perform the actions. Each browser was scripted to perform a random action from a predefined list of actions and immediately move on to the next action (ie. zero think time). Please note that it resulted in each browser performing substantially more tasks than would be possible by a real user and you should not equate the number of browsers to represent the number of real-world concurrent users.
Each test was run for 20 minutes, after which statistics were collected.
|JIRA Server||JIRA Data Center|
The environment with JIRA Server consisted of:
The environment with JIRA Data Center consisted of:
JIRA Server: 1 node
JIRA Data Center: 2 nodes
JIRA Data Center:
JIRA 7.9 scalability
JIRA's flexibility causes tremendous diversity in our customer's configurations. Analytics data shows that nearly every customer dataset displays a unique characteristic. Different JIRA instances grow in different proportions of each data dimension. Frequently, a few dimensions become significantly bigger than the others. In one case, the issue count may grow rapidly, while the project count remains constant. In another case, the custom field count may be huge, while the issue count is small.
Many organizations have their own unique processes and needs. JIRA's ability to support these various use cases explains the dataset diversity. However, each data dimension can influence JIRA's speed. This influence is often not constant nor linear.
In order to provide individual JIRA instance users with an optimum experience and avoid performance degradation, it is important to understand how specific JIRA data dimensions influence the speed of the application. In this section we will present the results of the JIRA 7.9 scalability tests that investigated the relative impact of various configuration values.
How we tested
As a reference for the test we used a JIRA 7.8 instance with the baseline test data set specified above and ran the full performance test cycle on it. To focus on data dimensions and their effect on performance, we didn't test individual actions, but instead used a mean of all actions. Next, in the baseline data set we doubled each attribute and ran independent performance tests for each doubled value (i.e. we ran the test with a doubled number of issues, or doubled number of custom fields) while leaving all the other attributes in the baseline data set unchanged. Then, we compared the response times from the doubled data set test cycles with the reference results. With this approach we could isolate and observe how the growing size of individual JIRA configuration items affects the speed of an (already large) JIRA instance.
Response times for JIRA data sets
Each row represents mean response times. The lower the value, the better the performance.
The number of issues affects JIRA's performance, so you might want to archive issues that are no longer needed. You may also come to conclusion that the massive number of issues clutters the view in JIRA, and therefore you still may wish to archive the outdated issues from your instance.
Backup and Delete - one JIRA instance
This is the quickest and easiest of the two methods. You simply take a JIRA backup of the entire instance, label the backup with the date and then store it in a secure location. Test that the backup can be restored on a JIRA test instance. Once you are satisfied that it all works you can go ahead and delete the projects or issues that are no longer in use. Deleting can also extend to the other dimensions such as custom fields, schemes, etc.
Although quick and easy, the downside to this method is that when you users request to see an archived issue you will need to find the appropriate backup and then restore it to another JIRA instance. This is the best method to use if you do not anticipate a large number of archive retrieval requests.
Migrate and Delete - two JIRA instances
This method is much more complicated. First, you will initially take a full backup, then restore this into a separate JIRA instance. Verify that everything has come across. Once you are happy you will keep the issues you want to archive in this instance and delete everything else. For future archiving sessions you will go to your production instance and create a filter for all the issues you want to archive. Move these issues into a separate project and then take a full backup of your JIRA instance. You will then use JIRA's project restore to import this project into the archive instance where you can then move these issues into their respective projects.
Although this method takes up a lot more time and resources, the main advantage is that you will essentially have a live archive instance that your users can visit anytime they want to see an archived issue.
For more information, see Backing Up Data.
As your JIRA user base grows you may want to take a look at the following:
- Connecting JIRA to your LDAP Directory for authentication, user and group management.
- Connecting to Crowd or Another JIRA Server for User Management.
- Allowing Other Applications to Connect to JIRA for User Management.
JIRA Knowledge Base
For detailed guidelines on specific performance-related topics refer to the Troubleshoot performance issues in Jira server article in the JIRA Knowledge Base.
JIRA Enterprise Services
For help with scaling JIRA in your organization directly from experienced Atlassians, reach out to our Premier Support and Technical Account Management services.
The Atlassian Experts in your local area can also help you scale JIRA in your own environment.