Details
-
Bug
-
Resolution: Fixed
-
Low
-
7.10.0, 7.13.0
-
7.1
-
Severity 3 - Minor
-
1
-
Description
Issue Summary
Steps to Reproduce
- Create JQL with project IN (...) clause, which contains long list of projects(id, key or name)
- Execute sequence of searches, increase number of projects in clause
Expected Results
Performance of search doesn't degrade
Actual Results
Search performance is degrading proportionally to number of projects.
Getting list of projects involved in JQL query is expensive:
2019-01-04 21:33:40,808 http-nio-8080-exec-18 DEBUG admin 1293x406x1 7uj3d3 89.64.38.139 /rest/issueNav/1/issueTable [c.a.util.profiling.UtilTimerStack] [113ms] - Searching and sorting with Collector
[113ms] - Lucene Search
[38ms] - Get Query Projects
[11ms] - Permission Query
[0ms] - DefaultJqlOperandResolver.getValues() - multivalue
[0ms] - MultiValueOperandHandler.getValues()
Note 38ms spent on getting projects from query, which is much more than 11ms spend on generating permission query based on that list.
Workaround
There is no workaround for this behaviour.
Attachments
Issue Links
- is caused by
-
JRASERVER-66270 Optimise permission queries for searches
- Closed
- relates to
-
FLASH-1211 Loading...