Scaling JIRA 7.5

On this page

Introduction

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:  

  1. Scale a single JIRA instance. 
  2. 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.

On this 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.
  • Configuration
    • 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.

Test environment

Our performance tests were all run on the same controlled isolated lab at Atlassian. For each test, the entire environment was reset and rebuilt, and then each test started with some idle cycles to warm up instance caches. 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 4minutes, after which statistics were collected. 

 

Click here for details of our test environment
Hardware Software
CPU x2: Intel(R) Xeon(R) CPU E5-2430L 0
@ 2.00GHz
Operating System Ubuntu Server 12.04 LTS
CPU Cores: 12x Database MySQL 5.5
CPU Threads: 24x JAVA platform Java 1.8.0
Memory: 6x 8GB DIMM DDR3 1333 MHz Browser Chrome


JIRA 7.5.0 vs 7.4.0 performance

In this section, we’ll compare JIRA 7.5.0 to JIRA 7.4.0. Specifically, we ran the same extensive test scenarios for both JIRA versions. The only difference between the scenarios was the JIRA version. 

The scenarios were focused either on different data sets used by JIRA, or on different actions performed.

 

Data sets

The following chart presents mean response times for a JIRA instance that used various data sets, a different one in each test. We wanted to show how particular data dimensions affect the performance of JIRA, that’s why instead of testing particular actions, we tested a mean of all actions (see Actions) for each data set. The data sets contained a different number of issues, workflows, users, and so on. You can check what exactly was in each of them below the chart.

Response times per data set

Each row represents mean response times. The lower the value, the better the performance.

 

Details of the baseline data set...

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.

The Analytics data did not contain information about agile boards and attachments, so we extrapolated them from the JIRA 6.4 scaling report by scaling them proportionally with issues.

The following table presents rounded values of the 999th permille of each data dimension. We used these values to generate a sample data set with random test data in  JIRA Data Generator.

JIRA data dimension Value
Issues 1,000,000
Projects 1500
Custom Fields 1400
Workflows 450
Attachments 660,000
Comments 2,900,000
Agile Boards 1,450
Users 100,000
Groups 22,500
Security Levels 170
Permissions 200
Details of how we built remaining data sets...

Every other data set was derived from the baseline. For each, we doubled one attribute while leaving all the other attributes unchanged. For example, in the “Projects” data set, we doubled the number of projects (3000), while in the “Workflows” data set, we doubled the number of workflows (900). "All data sets" is a mean of all data sets, and is used as the base for testing response times per action in the Actions section.

The following table presents the "Issues" data set to illustrate this.

JIRA data dimension Value
Issues 2,000,000
Projects 1500
Custom Fields 1400
Workflows 450
Attachments 660,000
Comments 2,900,000
Agile Boards 1,450
Users 100,000
Groups 22,500
Security Levels 170
Permissions 200
Conclusion

Performance of JIRA 7.5 is comparable to that of JIRA 7.4, regardless of the data set used. On average, the difference is less than 1%, mostly visible with issues, custom fields, and users & groups.

 

Actions

The following chart presents mean response times for different actions performed in JIRA. In this case, we wanted to show how particular actions affect the performance of JIRA, and we tested them on a mean of all data sets (see Data sets). An "action" in this context is a complete user operation like opening of an Issue in the browser window. You can check the details of these actions below the chart.

Response times per action

Each row represents mean response times. The lower the value, the better the performance.

 

Details of JIRA actions...

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...
description ~ 'totally' or summary ~ 'hobos' and comment !~ 'propel' ORDER BY key
reporter was in (admin) and status = Closed order by createdDate

 

comment ~ 'contest* saw' and reporter was admin order by assignee desc

 

text ~ 'a* ba*' ORDER BY Status, summary

 

priority was in (Low, Lowest) or (status = 'In Progress' and assignee changed) or createdDate > '2016/07/02 00:00'

 

resolution = Unresolved and priority = Low

 

text ~ 'witch* doctrine' and status was not Closed order by priority

 

project = novemcinctus and assignee = admin ORDER BY assignee

 

assignee in membersOf('users_1') order by project

 

not (status = closed and resolution = Done and priority = High)

Half of these queries are very heavyweight, which explains high average response time.

 

10
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. It's used as the base for testing   response times per data set in the Data sets section. -


Conclusion

Response times in JIRA 7.5 are comparable to those in JIRA 7.4, regardless of the actions performed. On average, the difference is less than 1%, mostly visible with such actions as viewing the dashboard or the project summary.

 

Further resources

Archiving Issues

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. 

Read about the two common methods to archive JIRA Issues....

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.

JIRA Data Center

JIRA Data Center is the ideal solution to use when you have a high number of concurrent users. JIRA Data Center allows the JIRA application to be clustered in a multi-node cluster where all nodes are active. This means that with a load balancer in front you can distribute the load across multiple nodes thereby increasing throughput when compared to a single server handling the same load. JIRA Data Center 7.5 also provides High Availability, and is the only fully Atlassian supported option for JIRA Disaster Recovery

Please refer to our main page for more information on JIRA Data Center.

User Management

As your JIRA user base grows you may want to take a look at the following:

JIRA Knowledge Base

For detailed guidelines on specific performance-related topics refer to the Troubleshooting Performance Problems 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.

Atlassian Experts

The Atlassian Experts in your local area can also help you scale JIRA in your own environment. 

Last modified on Sep 11, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.