Jira Project and Performance

[Balaji Sundaram]

Hi All,

We have set up 1 Jira project for close to 100 teams (~1000 members). 

On an avg, we have one person creating a ticket every day so ~20k tickets a month.

Am hearing now that this may cause performance issues as Jira is designed to load entire project data every time you hit a project (regardless of the issue). 

Hence the recommendation is to create a Jira project per team.  

Honestly, we have not encountered any performance issues yet.  
Can I please get recommendation from expert on size limitations on Jira project and in my scenario, am I going to encounter performance issues if I continue with current volume (as above) with just 1 Jira project?

note: we don’t run any external scripts or bill processing. 

many thanks looking into this! 

[Matt Doar · Accepted solution]

If you have enough heap allocated, your current use is unlikely to be a problem. We only create new projects when a different set of versions, components, admins or permissions are needed. Not just because a new team exists. 

[Nic Brough -Adaptavist-]

I'm a little concerned by where you saw "as Jira is designed to load entire project data every time you hit a project"

I don't think it's done that since Jira 3.something fixed a bug with "project summary is slow in large projects".   Although the bug where "default JQL to an empty query that took ages to realise it was being slow" persisted a lot longer...