Jira performance depends on multiple factors: user setup, network characteristics, data shape, and traffic. Here's how these factors affect application speed.

User setup

Client environment

Local hardware and software handle the heavy lifting of rendering the Jira interface.

• CPU core count: Jira runs complex code on your machine. Higher core counts allow the device to render pages faster.

• Browser: Browser engines differ significantly in speed. Updated browsers are optimized to execute code more efficiently than older versions.

• Operating system: Your OS manages memory and background resources. An outdated OS may struggle to allocate resources effectively to the browser.

Network speed and protocol

Network speed and protocol determine how fast data moves between Atlassian cloud and your device.

• Network speed: High bandwidth and low latency are required for a responsive experience. Slow connections delay initial data delivery.

• HTTP/1 vs. HTTP/2: These protocols dictate how data is transferred. HTTP/1 loads resources sequentially, which can cause bottlenecks. HTTP/2 loads resources in parallel, which is significantly faster for modern web applications like Jira.

Data shape

The complexity of your Jira data impacts processing time.

• Schemes and fields: A large number of field configuration and work type schemes increases the processing required to render experiences. Unused fields add unnecessary weight to the system.

• Data volume: Retaining unused projects and old work items bloats the dataset scanned during operations, increasing processing time.

• Query and access complexity: Complex project role permissions and slow board filters (often caused by suboptimal JQL) require intensive calculation, delaying page loads.

Traffic

Performance fluctuates based on concurrent usage. When many users access the system simultaneously, response times may increase as resources are shared.