I have a series of JIRA issues which take as much as 7 seconds to load, and I want to understand what is causing the performance issue.
When profiling the performance of the page, I notice that there are two identical calls which contain most of the loading times: Retrieve From cache/db and filter.
Is there a way to dig into what's actually happening during these calls? I assume that I need a greater level of detail to understand why some, but not all issues, take so long to be read from the cache.
[0ms] - PermissionManager.getProjectObjects()
[0ms] - PermissionManager.hasPermission()
[0ms] - PermissionManager.hasPermission()
[0ms] - PermissionManager.hasPermission()
[0ms] - PermissionManager.hasPermission()
[0ms] - PermissionManager.hasPermission()
[2145ms] - Retrieve From cache/db and filter
[104ms] - Lucene Search
[0ms] - IssueIndexManager.getIssueSearcher()
[104ms] - Lucene Query
[2159ms] - Retrieve From cache/db and filter
[112ms] - Lucene Search
For posterity, there was a condition using a JQL query that was causing the slow loading.
This was the reason for the page being slow to load and not just for actions such as transitions.
Hi Daniel, how did you find out which JQL it was?
We experience the same. When clicking on an issue in an Agile board, the issue is shown within half a second, but when I open the issue in a new tab, it takes 6 to 7 seconds to open. Opening the Agile board itself also costs about 10 secs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Daniel, can you please provide more details about "there was a condition using a JQL query that was causing the slow loading". How JQL condition is related to Issue load time? Was it caused by any plugin?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@DanielG - what condition using a JQL query? a search condition or a plugin that was specifically making the call? @M Hoogenboom and @Aliaksei Shorkin and I all appear to be in the same boat... not sure if they found anything out at this point...
Any assistance appreciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With the caveat that this was a few years ago - there was some trickery being done where the transition options were based on JQL queries, in a project which had issue-level security enabled, so Jira ran the query on page load and it was really expensive.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Sometimes certain plugins slows down the loading if the issue has a large change history, the only way I know to get more level of detail is by using a profiler like jprofiler.
i had this problems several time, what I do is:
But first of all make sure your db connectivity and latency are correct and the io performance is ok based on atlassian parameters ( there's an io testing tool from atlassian)
hope you can find the solutions, this problems gave all of us insight to solve future problems
is this a very large instance?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.