How fast does Jira respond? The load simulation by catworkx provides answers

Fast access and response times – a crucial criterion when selecting new software for a company. The load simulation by catworkx aids in the decision-making process, as it tests not only static but also dynamic content of Atlassian software, such as Jira. It's also an important measurement tool in later use – because the load simulation can be reused.

When searching for a new tool for requirements, change, and test management within a business unit, a major German manufacturer of automotive accessories also considered Atlassian's Jira software as a potential solution. Before implementation, the manufacturer wanted to test whether Jira met the requirements of their own company and could be used as a new tool across the entire business unit or in specific areas

For this evaluation, the company commissioned catworkx, an Atlassian partner, to conduct a load simulation. This load test was intended to examine the stability and performance of Jira within the technical and operational framework specified by the company. As a long-standing partner of Atlassian, catworkx has extensive experience in the implementation and maintenance of Jira and is one of the few providers capable of performing such a load simulation.

To carry out the load simulation, the catworkx team worked closely with the company. In an initial step, they jointly defined which use cases should be tested in the simulation and whether these corresponded to real processes within the company. After clarifying further points, such as the existing or necessary IT infrastructure, the access locations, and the required measurement systems, the defined use cases were recorded based on the HTTP stream. These recordings were then adapted and made usable for later reuse.

While many measurements for software response times often only access static data, the load simulation developed by catworkx stands out because it allows static and dynamic content to be used and simulated over a longer period within a Jira instance. In graduated steps, not only was the number of simultaneously working users increased, but also the application's content – such as the number of projects, issues, or fields used in Jira – was scaled. Additionally, the test was conducted from various locations within the company

Such a simulation of various use cases, specified by the company, created a basis for comparing the performance behavior of Jira. The collected measurements were centrally recorded and evaluated in a database. To assess and analyze Jira's performance, these measurement results were also graphically visualized.

The catworkx load simulation, tailored and adapted to the company's requirements, provided crucial decision-making support for the implementation of Jira. But that's not all: the company can re-evaluate the stability and performance of their Jira instance following future changes. Furthermore, parts of the simulation can be reused in cyclical runs to verify Jira's responsiveness.