---
title: "[Xray] What Are the Differences Between Xray Server/Data Center and Cloud Regarding Performance and Data Residency?"
canonical: "https://docs.getxray.app/space/ProductKB/333938731/%5BXray%5D%20What%20Are%20the%20Differences%20Between%20Xray%20Server%2FData%20Center%20and%20Cloud%20Regarding%20Performance%20and%20Data%20Residency%3F"
format: markdown
---
# Data Storage Differences

When using **Xray Server/DC**, most Xray data is stored in Jira custom fields, within the same database as Jira itself. This means:

- Access to Xray data is very fast, as it is retrieved directly from the local Jira database.
- Since the Xray data is part of the Jira Issue record, it loads at the same time as the Issue itself.

In **Xray Cloud**, the architecture is different. Atlassian does not store third-party app data on its own servers, as it has no control over that data. As a result, Xray data is stored separately from Jira’s data, on Xray Cloud servers. This means:

- All information previously stored in Jira custom fields has been replaced with Xray entities.
- These entities are stored outside Jira, on Xray’s own infrastructure.

# How Data Loads in Xray Cloud

When you open an Issue or a panel, such as the [Testing Board](https://getxraydocs.atlassian.net/wiki/pages/createpage.action?spaceKey=XRAYCLOUD&title=Understanding%20the%20Interface) or the [Test Run](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565109) screen:

1. Jira Issue data is retrieved from Atlassian’s servers via API.
2. Once that completes, a separate API request is sent to Xray servers to fetch the related Xray data.

> ℹ️ The total loading time is therefore: the time to retrieve a Jira Issue data + the time to retrieve Xray data.

Because of the Cloud architecture, there will always be a slight delay between Jira issue data loading and Xray data appearing. Xray continuously works to reduce this delay, and every Xray Cloud release includes performance improvements toward that goal.

## Typical Response Times

[Xray API](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565892) response times are considered normal when they range between **1000 ms and 2000 ms**, with occasional spikes slightly above this range (these values might vary, being slightly above or lower does not mean instant low performance).

When evaluating Xray Cloud performance, Xray focuses on **individual API call times**. For example:

- Loading the **Test Run** screen may require multiple API calls to fetch attachments, iterations, and defects.
- Even if each call completes in under one second, the total load time for the page may exceed one second due to the number of calls involved.

#### Xray Cloud Domains

- Global: `https://xray.cloud.getxray.app/`
- US: `https://us.xray.cloud.getxray.app/`
- EU: `https://eu.xray.cloud.getxray.app/`
- Australia: `https://au.xray.cloud.getxray.app/`

### Data Residency and Performance Impact

By default, Xray Cloud data is stored on our servers in **North Carolina, US**. With **[Data Residency](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565771)**, you can choose to store your Xray data in:

- **Europe** (Germany).
- **Australia **(Sydney).

> ℹ️ **Placing your Xray data closer to your users can reduce network latency and improve loading times.**