Performance for x-ray

[Pooja Bhandari]

Any idea of the performance for x-ray. Actually it resides in jira and as our testing grows with huge test cases  it might impact performance. 
Does anyone have experience on it and answer me ? 
TIA

[Nikola Perisic]

Hello @Pooja Bhandari 

Couple of questions:

• What do you mean by the performance of x ray?
• Are you using an enterprise version?

The more information you have the better.

[Pooja Bhandari]

Hi @Nikola Perisic 

• By performance I mean if we have more number of test cases in x-ray , will there be any difference in speed of accessing x-ray
• Yes it will be a cloud

[Nikola Perisic]

In their official documentation it doesn't mention anything about the performance. Therefore, you might need to contact their support, since this is tied to their architecture where there is not much information.

Link: https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2

[Oliver Thomys]

Hello.

I have worked with Jira Data Center and the associated Xray instance for many years. We had no problems with the performance there.

It's been a few months since I've been working with Jira Cloud and Xray Cloud for the first time. Unfortunately, my experiences are much worse there. This is because it takes a very long time for the Xray-specific fields to load. This means that standard Jira fields such as "Description" or "Priority" load very quickly, but Xray fields such as "Test Steps", "Test Coverage" or "Linked Test Executions" take an average of 7 seconds to be displayed.

We are currently analysing where the delay is coming from – i.e. whether it is due to our infrastructure or Xblend.

I hope to have helped you with this.

[Katy Bradley]

I have a very similar experience with X-Ray performance on Jira Cloud. It's pretty painfully slow sometimes and I have to refresh the ticket multiple times to get the x-ray fields to display.

@Oliver Thomys did you discover anything from your analysis, looking for a direction to start in. Thank you!

[Oliver Thomys]

Hello Katy.

Unfortunately, light and shadow are close together. On the positive side, Xblend's support read my post and actively approached us about the problem. This was followed by a joint session with our Jira admins. There we discussed the problem.

Xblend is unfortunately aware of the problem. They said that Atlassian has implemented the Jira Cloud in such a way that the Jira specific fields are loaded first. Only then the fields of plug-ins. Unfortunately, this takes time. In addition, Xblend probably has no influence on the order in which the fields are loaded. This means that the Jira fields may be loaded first, then the fields of 10 other plug-ins, and only then the Xray fields.

They had just a little tip. We hosted Jira in Europe and part of our plug-ins in America. In other words, they were physically far apart from each other. We were advised to host all data on one continent or in one country.

I hope this helps you a bit.

Maybe the diligently reading colleagues from Xblend will add something.

Best regards

Oliver