Jira application performance

[Indrasenareddy k]

Jira application performance issue for project.
Now it takes too much time to launch a new screen or select any other issue types on left pane.
But similar JIRA type other applications are much faster for performing same operation.

[Vitalii Rybka]

Hi @Indrasenareddy k,

Adding to Philipp's excellent advice, here are some quick performance checks you can do:

Immediate troubleshooting:

• Clear browser cache and try incognito mode
• Check if the slowness affects all users or just specific ones
• Test during off-peak hours to see if it's load-related

Project-specific issues to check:

• Large number of custom fields or complex workflows
• Permissions schemes with too many groups/users
• Heavy dashboards or filters loading on project pages
• Large attachments or excessive issue history

Quick wins:

• Disable unnecessary project features/apps
• Archive old/inactive issues if possible
• Check if specific issue types have complex field configurations

For admins:

• Monitor JVM memory usage and garbage collection
• Check database query performance logs
• Review app/plugin resource consumption

Since you mentioned other Jira instances are faster, it's likely configuration or resource-specific rather than a general Jira issue.

If you need help with specific performance monitoring or optimization strategies, feel free to DM me!

Hope this helps narrow down the issue!

[Philipp Sendek]

Hi @Indrasenareddy k ,

Performance issues in Jira can have various reasons and it's not easy to provide you with a solution with the information you've provided.
The first thing I'd recommend is for your system administrators to check the assigned resources for your Jira application against the recommendations by Atlassian here: https://confluence.atlassian.com/enterprise/data-center-infrastructure-recommendations-972333478.html

Maybe this already provides helpful ideas. 

Apart from that, it could be anything from the server not having enough resources available to operate Jira, memory being overcommitted and the system outsourcing data from memory to the disk (swapping) or issues with the database connection or the load on the database itself.

Also the sizing of the Heap and MetaSpace could be something to look into.

While this is of course something that your system administrators can tackle with the help of Atlassian's documentation, it might also be a good idea to contact a Solution Partner in your area to help you troubleshoot your system performance.

Greetings
Philipp