[null, {"document_url": "https://confluence.atlassian.com/conf61/confluence-data-center-performance-877188849.html", "unformatted_src": "/conf61/files/877188849/877188851/1/1489127363972/DataCenterPerformance.png", "src": "https://confluence.atlassian.com/conf61/files/877188849/877188851/1/1489127363972/DataCenterPerformance.png", "formatted_filename": "DataCenterPerformance"}, null, {"document_url": "https://confluence.atlassian.com/conf61/confluence-data-center-performance-877188849.html", "unformatted_src": "/conf61/files/877188849/877188850/1/1489127363893/DataCenterBarGraph-v2.png", "src": "https://confluence.atlassian.com/conf61/files/877188849/877188850/1/1489127363893/DataCenterBarGraph-v2.png", "formatted_filename": "DataCenterBarGraph v"}, null]


Confluence Data Center Performance

Confluence Data Center






This document describes the performance tests we conducted on Confluence Data Center within Atlassian and the results of those tests. You can compare these data points to your own implementation to predict the type of results you might expect from implementing Confluence Data Center in your own organization.

We started our performance tests by taking a fixed load profile (read/write ratio), then tested different cluster set ups against multiples of that load profile.


Testing results summary

Performance gains - Under a high load, clustered Confluence has improved performance overall.

Request responses don't diminish under increased load - Adding more nodes increases throughput, handles higher load and decreases response times. You might observe a different trend/behavior based on your configuration and usage. For details, please see the  What we tested section below.

Testing methodology and specifications

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


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 the following components and configuration:

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 creating a page or 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

Tests were performed with differing load sizes, from 4 up to 96 browsers. For larger load sets, profiles were scaled up, that is, doubling each amount for the 24 browser load, tripled for the 36 browser load.

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


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

Hardware testing notes:

Comparison to Confluence Server response times

The following table shows the relative performance as the load increases for each Confluence instance configuration: Confluence Server, two node Confluence Data Center, and four node Confluence Data Center. The table shows the response time relative to the baseline response time which we determined to be Confluence Server with sixteen browsers. 
For a detailed overview of Confluence's clustering solution see Confluence Data Center Technical Overview. For help with installation, take a look at Installing Confluence Data Center.



