JIRA Data Center Performance

This document describes the performance tests conducted on Data Center within Atlassian and the results we found.

We aimed to test concurrent load - hoping that as we increased the number of users, we saw better overall performance compared to the same number of users in a server instance.

You can compare these data points to your own implementation to predict the type of results you might expect from implementing Data Center in your own organization.

We started our performance tests by determining what JIRA Server's baseline number is. We determined this by putting JIRA Server under different level of loads until we saw a sizable decrease in performance. We then installed Data Center onto the same hardware and ran the same set of performance tests. 

Further below you will find more detailed information on hardware specs, load statistics, response times, and our testing methodology.

 

 

Testing results summary

  • Under a high load, clustered JIRA has improved performance overall.
  • Throughput and capacity show a near linear increase as nodes are added to the cluster.
  • Specific actions show varying improvement in response times. For details, please see Testing results for specific actions.
  • You might observe a different trend/behavior based on your configuration and usage. For details, please see What we tested.

Testing methodology and specifications

The following sections detail the testing environment and methodology we used in our performance tests.

How we tested

Our performance tests were all run on the same controlled isolated lab at Atlassian. For each test, the entire environment was reset and rebuilt. The testing environment included installing the following components:

  • Apache load balancer 
  • Postgres database and the required data
  • Clustered JIRA on one, two, or four machines as required for the specific test
  • Chrome browser on 'x' number of machines as required to generate the load for the specific test

To run the test, we used a number of machines in the lab to generate load using scripted browsers and measuring the time taken to perform an action. An action here, means a complete user operation like adding comment. Each browser was scripted to perform an action from a predefined list of actions and immediately move on the to next action (i.e. zero think time). Please note that this resulted in each browser performing more tasks than would be possible by a real user and you should not interpret the number of browsers to be equal to the number of real world users. Each test was run for 20 minutes, after which statistics were collected.

What we tested

  • All tests used the same Postgres database containing:
    • 550 projects
    • 628 custom fields
    • 450,000 issues
    • 10,000 users in total
  • The mix of actions we included in the tests represented a sample of the most common user actions* representing three typical types of users: Issue Browser, Issue Creator and Project Manager. The table below show the ratio of actions performed by each of these users. These user-based actions were repeated until the test was completed.
Operation
Issue Browser
Issue Creator
Project Manager
View Dashboard 55 10 15
View Issue 60 55 10
Browse Project 20 20 20
Issue Search 20 20 0
Edit Issue 2 5 2
Add Comment 2 2 5
Search All 10 10 10
Search Large 5 5 10
Search Small 5 5 10

* The tests do not include admin actions as these are assumed to be relatively infrequent. 

Hardware

All performance tests were all run on the same controlled, isolated lab at Atlassian using the hardware listed below.

Hardware Description How many?

Rackform iServ R304.v3

CPU: 2 x Intel Xeon E5-2430L, 2.0GHz (6-Core, HT, 15MB Cache, 60W) 32nm

RAM: 48GB (6 x 8GB DDR3-1600 ECC Registered 2R DIMMs) Operating at 1600 MT/s Max

NIC: Dual Intel 82574L Gigabit Ethernet Controllers - Integrated

Controller: 8 Ports 3Gb/s SAS, 2 Ports 6Gb/s SATA, and 4 Ports 3Gb/s SATA via Intel C606 Chipset

PCIe 3.0 x16: Intel X540-T2 10GbE Dual-Port Server Adapter (X540) 10GBASE-T Cat 6A - RJ45

Fixed Drive: 240GB Intel 520 Series MLC (6Gb/s) 2.5" SATA SSD

Power Supply: 600W Power Supply with PFC - 80 PLUS Gold Certified

20

Arista DCS-7050T-36-R 4PORT SFP+ REAR-TO-FRONT AIR 2XAC 1
HP ProCurve Switch 1810-48G 48 Port 10/100/1000 ports Web Managed Switch 1

Hardware testing notes:

  • In order to quickly put more stress on the JIRA nodes with less load, cluster nodes were set to use only 2 cores out of 6 from each CPU, thereby reducing its processing power to one-third.
  • For JIRA instances being tested, 9 GB of memory was allocated to the JVM consistently across all tests. This may not be optimized for all cases but allowed for consistency and comparability between the tests. 
  • During the tests we did not observe high CPU or IO load on either the database or load balancer servers.
  • During the tests we did not observe running out of HTTP connections in the load balancer or connections to database.
  • The browser and servers are in the same location so there was very low latency between client and server.

Testing results for specific actions

The following tables show the relative performance of the various actions in the tests as the load increases for each JIRA instance configuration: JIRA Server (one node equivalent), two node Data Center, and four node Data Center. Each table shows the response time relative to the baseline response time which we determined to be JIRA Server with six browsers. 

Average for all actions

Browsers JIRA Server 2 node 4 node
6 100.00% 97.63% 99.41%
12 109.92% 99.55% 100.35%
18 137.32% 108.30% 107.79%
24 178.13% 122.64% 120.54%
36 259.39% 129.68% 113.31%
48 336.33% 157.54% 123.83%
60 447.72% 190.16% 125.77%
72 577.57% 223.79% 135.91%
84 590.47% 264.84% 147.04%
96 681.24% 313.20% 161.61%
120 986.29% 394.29% 194.44%
144 1067.97% 483.54% 231.73%

Edit Issue

Browsers JIRA Server 2 node 4 node
6 100.00% 97.98% 100.27%
12 119.82% 108.28% 103.99%
18 156.21% 116.12% 113.90%
24 215.45% 133.92% 125.92%
36 330.24% 148.21% 119.67%
48 447.96% 188.60% 134.30%
60 607.33% 238.56% 143.38%
72 776.20% 286.16% 155.23%
84 818.90% 342.68% 173.00%
96 1063.00% 403.19% 194.96%
120 1598.56% 565.08% 244.13%
144 1688.77% 687.53% 293.61%

Add Comment

Browsers JIRA Server 2 node 4 node
6 100.00% 94.20% 95.75%
12 114.67% 100.81% 97.57%
18 139.09% 109.38% 103.83%
24 179.78% 122.22% 117.59%
36 260.49% 133.38% 111.90%
48 379.78% 162.47% 125.01%
60 507.62% 201.25% 124.67%
72 718.05% 237.92% 140.50%
84 660.83% 293.28% 149.58%
96 840.17% 354.80% 168.17%
120 1381.26% 469.93% 204.08%
144 1413.76% 570.71% 251.35%

Browse Project

Browsers JIRA Server 2 node 4 node
6 100.00% 79.41% 79.21%
12 116.55% 82.64% 82.42%
18 158.18% 91.11% 88.24%
24 220.40% 104.56% 98.88%
36 356.34% 123.76% 96.58%
48 491.48% 173.63% 107.47%
60 659.75% 227.44% 115.75%
72 834.75% 286.28% 131.55%
84 888.91% 362.51% 154.61%
96 930.16% 452.95% 178.92%
120 1442.93% 571.17% 238.08%
144 1662.80% 705.98% 301.82%

Search that returns less than 50 issues

Browsers JIRA Server 2 node 4 node
6 100.00% 100.82% 100.61%
12 113.41% 104.47% 104.06%
18 140.66% 113.85% 112.05%
24 182.50% 127.73% 124.44%
36 275.71% 137.37% 116.22%
48 358.93% 171.67% 129.92%
60 488.90% 207.66% 128.43%
72 614.09% 247.31% 146.45%
84 622.33% 296.83% 159.23%
96 757.55% 352.28% 175.98%
120 1141.50% 454.47% 214.49%
144 1300.34% 557.60% 258.20%

View Issue

Browsers JIRA Server 2 node 4 node
6 100.00% 101.22% 103.82%
12 107.11% 101.86% 103.44%
18 127.01% 109.92% 110.22%
24 155.76% 123.45% 122.76%
36 196.87% 126.12% 116.52%
48 242.91% 142.18% 123.71%
60 317.13% 159.44% 125.37%
72 411.03% 177.93% 130.27%
84 413.06% 201.73% 136.61%
96 496.37% 229.18% 144.99%
120 740.60% 277.99% 163.38%
144 796.60% 334.75% 184.49%

Issue Search (search by issue ID)

Browsers JIRA Server 2 node 4 node
6 100.00% 100.89% 105.29%
12 109.61% 102.08% 104.19%
18 135.45% 110.86% 111.02%
24 176.18% 124.19% 122.15%
36 234.05% 133.67% 118.15%
48 299.84% 155.20% 124.64%
60 394.66% 182.18% 130.64%
72 519.33% 207.54% 135.92%
84 539.22% 239.95% 148.16%
96 615.94% 277.13% 159.66%
120 933.86% 348.23% 184.66%
144 1030.52% 418.95% 214.84%

View Dashboard

Browsers JIRA Server 2 node 4 node
6 100.00% 98.43% 98.88%
12 110.66% 105.67% 104.63%
18 135.56% 118.87% 120.23%
24 167.02% 142.08% 141.98%
36 204.21% 129.91% 119.86%
48 252.82% 159.80% 145.79%
60 323.35% 177.79% 133.61%
72 413.18% 201.61% 155.90%
84 416.77% 230.13% 154.53%
96 526.65% 262.53% 174.27%
120 697.47% 312.61% 200.08%
144 863.23% 384.14% 233.81%

Search that returns all issues

Browsers JIRA Server 2 node 4 node
6 100.00% 96.34% 98.07%
12 113.79% 102.10% 101.99%
18 151.62% 112.81% 111.22%
24 207.04% 130.05% 127.50%
36 367.99% 140.95% 117.32%
48 487.86% 180.38% 131.27%
60 682.55% 239.24% 131.74%
72 872.30% 289.60% 146.17%
84 899.12% 354.19% 161.70%
96 1097.92% 435.01% 184.08%
120 1484.46% 567.04% 232.11%
144 1665.42% 731.34% 293.27%

Search that returns more than 45,000 issues

Browsers JIRA Server 2 node 4 node
6 100.00% 98.93% 99.36%
12 112.69% 102.01% 102.56%
18 151.92% 111.17% 112.01%
24 222.94% 127.98% 125.49%
36 425.99% 141.29% 114.85%
48 572.35% 196.86% 130.77%
60 764.37% 270.30% 132.00%
72 987.87% 355.97% 150.90%
84 998.83% 428.49% 172.20%
96 1035.99% 530.10% 201.53%
120 1314.94% 698.98% 275.21%
144 1347.68% 849.63% 354.15%

Ready to get started? 

Get going with Data Center straight away.

Last modified on Jul 6, 2016

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.