JIRA Software 7.6 Long Term Support release performance report

Before we started the test, we needed to determine what size and shape of data set represents a typical large JIRA instance. 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 following table presents rounded values of the 999th permille of each data dimension. We used these values to generate a sample dataset with random test data in JIRA Data Generator.

Baseline JIRA data set

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.

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)

The performance tests were all run on a set of AWS EC2 instances. 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. 

Here are the details of our test environment: