Jira Cloud performance with over 1M issues

[Shay Yacobinski]

Hi all,

We're researching if we should migrate some of our operation as issues managed in Jira, and are worried about possible performance trouble. I found a sizing guide for Jira Server but not for Cloud:
https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html?_ga=2.24846202.133988477.1577971499-838523241.1576677826

We plan on creating about 1M issues, possibly on the same project. Most of the issues will not be resolved. We won't have many users and will have a few dozen custom fields.
The number of issues will grow with time and may reach tens of millions.

How will this affect the overall performance of the board and ticket handling?
Is there a sizing guide for Cloud?

Thank you.

[Petter Gonçalves · Accepted solution]

Hello Shay,

Thank you for reaching out.

As you may know, Jira Cloud runs on Atlassian Servers, so a sizing guide would not give you any relevant information on what you should be measuring against it. Explaining it better:

JIRA Cloud has different plans that will adapt to your current necessity (2GB, 250G, Unlimited), giving you the storage and resources you need to achieve your goal. You can check the documentation below to know about the plans and how you can track your current storage in your site:

Storage for Jira and Confluence Cloud 

As you can see in the documentation, even if you reach the storage limit of your current plan, we won’t cancel your subscriptions or remove any data, as long as the usage is in accordance with our acceptable use policy.

That being said, storage does not cause performance issues and Jira is completely able to handle millions of issues without any performance gaps. Usually, only a huge usage of external scripts for bulk operations and Automation could cause such overload, although this is far from common.

Let us know if you have any questions.

[Robert Davenport]

@Petter Gonçalves, 

Does Atlassian recommend limiting the number of active issues in a Service Desk project?  Given performance impacts and time to reindex associated with SLA changes, Automation, etc., what is the recommended/suggested project size before archiving should be instituted for Service Desk projects?

[Petter Gonçalves]

Hello @Robert Davenport

There are no limits or recommendations for archiving projects in Jira since the number of issues in a specific project will not affect the performance, but yes the total storage data you have in your site.  In fact, the project archiving is a feature created to keep the search and organization of the issues in a better format, not to prevent any performance issues.

That being said, keeping your data storage under the limits of your plan as described in the documentation above should prevent any possible performance issues.