Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Persistent, widespread performance degradation (slow page loads, slow search/board rendering)

John Smith
August 8, 2026
Persistent, widespread performance degradation (slow page loads, slow search/board rendering) on a single-node Jira Software 9.12.13 Data Center instance used company-wide across Development, CRM, HR, Commercial, and Finance teams (~500–2,000 users).
Our Jira Software Data Center 9.12.13 instance (Jira Core 9.12.13, Jira Service Management 5.12.13, Confluence 8.5.15) is experiencing recurring, widespread performance degradation — slow page loads, slow issue navigator/board rendering, and slow search — reported by users across all departments (Dev, CRM, HR, Commercial, Finance) that rely on this instance for their core workflows.

Environment:
Single-node Data Center deployment (not clustered)

 

PostgreSQL database
~500–2,000 licensed users
Heavy attachment usage across projects
Several apps installed, including Timepiece – Time In Status and eazyBI

 


We are not able to change our platform/tooling — we need guidance on tuning, scaling, and capacity planning for our current Data Center deployment (e.g., whether our single node is undersized for this user count/workload, JVM/heap and GC tuning recommendations, database tuning, attachment storage best practices, and whether moving to a clustered DC deployment — which stays within our current licensing — would meaningfully help). We'd also appreciate guidance on how to identify whether any installed apps are contributing to the slowdown.

We understand Jira 9.12 has passed its DC end-of-life date; we're (slightly) open to upgrade recommendations as part of the fix [prefer not to, though], but need this decoupled from a "just migrate to Cloud" answer since that's off the table for us.

1 answer

0 votes
Arkadiusz Wroblewski
Community Champion
August 8, 2026

Hello @John Smith

With the scope of the degradation you're describing, I wouldn't recommend making JVM, database or clustering changes based only on suggestions from a Community thread.

Adding nodes won't help if the bottleneck sits at the database or storage level.

Collect diagnostic data (Support Zip, thread dumps, GC logs) and have Atlassian Support or a Solution Partner run a formal assessment. Also note that Jira 9.12 reached EOL in November 2025, so plan an upgrade to a supported Data Center version.

For a company-wide Data Center instance supporting many business-critical workflows, a proper performance assessment of the actual installation is the appropriate next step. 

We have too less information.

Best,

Arek 🤠

Suggest an answer

Log in or Sign up to answer