This page describes the performance and scale testing requirements for Data Center apps in Atlassian Marketplace. For a general overview of Data Center app development, see Developing apps for Atlassian Data Center products.
To aid in our evaluation of your performance testing, you will need to:
Latency Performance Results
Please provide the following test results in the format of the chart below.
Table of results
To submit your table of results, follow the below format:
|Endpoint||Type of call||Action||Response time without app installed||With app installed|
The purpose of Scale Testing is to reflect how the customer experience is impacted when operating across multiple nodes. To do this, you will be required to run scale testing on your app.
For many apps and extensions to Atlassian products, there shouldn't be a significant performance difference between operating on a single node or across many nodes in a Data Center deployment. To demonstrate the performance impacts of operating your app at scale, we require testing your Data Center app in a cluster. This simple test should perform the end user actions and API actions that are present in the Performance testing, as a multi-pass test against a cluster deployment.
If you are unfamiliar with deploying a Data Center environment, you can use either:
The results of this testing stage will provide you with an understanding of how use of your app is impacted across a Data Center cluster deployment depending on the configuration. At a minimum, you will need to test your app with the following configuration in Data Center:
It's advisable to configure your Data Center deployment using a load balancer to ensure you are deploying in an environment that mirrors a customer deployment. See the below basic diagram of a cluster of Jira Data Center nodes behind a load balancer.
Note however, that you will need to perform testing against each individual Jira Data Center node, so you will need to ensure that each node is configured to accept traffic directly to it and that by contacting each node directly you are likely to cause a dialogue to appear on each node as you access it. Jira is likely to give you an error such as this: JIRA Displays an Error Banner about the Base URL, as will each Data Center product in the Atlassian stack. Get to know more about these tips and more as you work through your deployment.
Once you have completed running your end user and API requests from your Performance stage, you will need to collate the response times together and submit these as part of your Data Center App Readiness submission.
To submit your results, follow the below format:
|Endpoint||Type of call||Action||Response time (single node)||Response time (2 nodes)||Response time (4 nodes)|
Atlassian specific performance testing tools are not currently available for all products. Below is a table of currently available tools published by Atlassian which have been used to provide some performance testing results on our products.
|Bitbucket Data Center, Confluence Data Center||The Atlassian Performance Testing Framework (formerly E3) provides Data Center App developers with a framework for performing testing scenarios against different configurations. It is currently a community led project that does not receive active support from Atlassian.|
|Jira Data Center||Jira Performance Testing Framework, is not currently publicly available. You can sign up for the beta in the Atlassian Community.|
For generic request testing like this, we encourage you to use leading performance and quality testing products available.