Performance issue while on admin accounts

[jacekmusial]

I have jira (v7.7.0#77001-sha1:3be3151) installed with jira-worklog-query-plugin, and lots of data (projects, issues) inside. Recently this instance was re-indexed.

When I'm logged to user who have admin rights, simple query http://jira/rest/jira-worklog-query/1/find/worklogs?startDate=2018-03-20&user=XYZ results in clogged jira.
Even after closing browser tab after one or two second after firing this query, Jira is still working on something.

But on the other hand, when I'm logged onto usual Jira user, firing the same query as above works like a charm. Valid Json is returned after very little short of time.

[bordatesz]

Hello there,
Thank you for reporting this. We will look into it in the future.

[jacekmusial]

There is Jira from 2016 stating that there should be index on STARTDATE in worklog table.
https://jira.atlassian.com/browse/JRASERVER-60817
It might be related. I'll be running some tests trying to extract informations about which SQL query is causing this downfall of efficiency, when running as admin.

[jacekmusial]

Adding index column on jira's internal WORKLOG table is plain simple solution, although not recommended. Unfortunately, Atlassian doesn't allow this action as it does violate Jira warranty.
Long story short, the settlement is to query directly Jira database, table WORKLOG and extract information manually.

I'll be glad to hear other people's solution to this performance issue.

[bordatesz]

It's good to know. Customers using larger instances have already send feedbacks about performance issues. We will look into that how we can optimize our queries in the knowledge of this information.