Shorter project keys improves JIRA performance?

[Niranjan Babu]

Hi All,

Do you feel that shorter project keys can help to improve JIRA performance, by reducing the search time of issues or while refreshing filters? What are the best practices that can be considered for a large JIRA instance?

Reducing the bulk update count is one thing that we are thinking about. Anything else? Thanks

Regards

Niran

[Pavel Junek · Accepted solution]

Hi @Niranjan Babu,

I don't think the length of the Projct key would affect Jira Performance. Jira Performance is influenced mainly by the amount of data, Custom Fields, the number of Permission schemes, etc.

Please see these links:

• Performance and scaling
• Best practices for scaling Jira Software
• Best practices for performance troubleshooting tools

Pavel

[Nic Brough -Adaptavist-]

I think @Pavel Junek has got the right answer here.  The project key is processed as a short string, and although mathematically a 10 character string imposes a bit more load than a 2 character string, there is no way a human will notice the 3 or 4 milliseconds overhead.

You'll gain more from simplifying the permissions in one arbitrarily chosen prjoect than you would by shortening all your project keys to 3 characters

[Niranjan Babu]

Thanks @Pavel and @Nic Brough -Adaptavist-

Is there a DB query to identify the Scrum or Kanban boards which has got multiple projects in their JQL board filter query. 

Consider the below queries

Project=ABC and status = Closed OR component is empty

Project=ABC and (status = Closed OR component is empty)

While the second one is the actual query to be used, users by mistake, if they use the first one in a agile board/filter/dashboard that would consume more resources. Am I correct? Identify these boards and fixing the JQL help to improve performance in a very large instance? Any thoughts please?

[Nic Brough -Adaptavist-]

Yes, you could do this with database calls, but, well, don't.  Jira's "database" is not, it is just a datastore, and is very very very very very very very very  not built for anything resembling reports.  If you're "reporting" from the database, there is a 99.9% chance that you're wrong.  And I'm being generous there.

The Jira Software API enables a lot of reporting - please do try that, and let us know if you get stuck?