Details
-
Bug
-
Resolution: Fixed
-
Low
-
8.20.0, 9.4.0, 9.12.5
-
None
-
8.2
-
Severity 3 - Minor
-
Description
Issue Summary
This is reproducible on Data Center: yes
This is a scope split of JRASERVER-73769.
Steps to Reproduce
- Populate the label table with millions of entries
- Expand the dropdown of a Label field in any Issue and observe how it takes long to run and the Thread is high on CPU load on the server
Expected Results
The autocomplete would not take so long to run everytime.
Actual Results
The thread becomes long running on the server and is usually not even useful to the end-users, as they may start typing labels to narrow the search, but the original request is still running.
Workaround
Currently, the only way to spare the server (and end-users) of these empty requests is to block them in the Proxy or Jira:
Attachments
Issue Links
- relates to
-
JRASERVER-73028 Portfolio plan load performance is impacted when a custom filed of type label is used in configuration.
- Gathering Impact
- split from
-
JRASERVER-73769 Label suggestions performance grows slow linearly as Jira scales
- Gathering Impact