Page History

...

•  - major
•  - highest
•  - high
•  - medium
•  - low
•  - lowest

...

A large number of Xray issues and Jira's performance impact

The number of issues is usually an indicator of how the size of a Jira instance performs under a high loadand a possible culprit for performance degradation. Yet, there are so many other elements that can affect the scale of a JIRA instance, such as the number of users, workloads, etc.

Xray uses issue types to map the majority of its entities. Tests, Preconditions, Test Sets, Test Plans, and Test Executions are all issues in Jira. This means that having many Xray issues can also affect Jira's overall performance.

Nevertheless, the Xray issue types can affect Jira's performance in different ways. We expect expect Tests, Preconditions and  and Test Sets to  to have a lesser impact than than Test Plans or  or Test Executions.

If customers are importing automated execution results into Xray daily (for several projects and teams), the number Test Execution issues will grow significantly over a relatively short period.

A large number of Test Plans and Test Executions can affect Xray test status and coverage calculations, thus contributing to Jira's overall performance.

Test Plans aggregate and consolidate the results of the related Test Executions and Tests. Therefore, the overall number of Test Runs can add some overhead to the calculation of the consolidated results.

Below we provide some tips on how to scale Xray.

Jira specifics

 Xray is built on top of Atlassian's Jira, therefore it is mostly dependant on the architecture and technologies followed by Jira itself.

...