Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
44
-
4
-
Description
Summary
JIRA inefficiently populates fieldLayoutCache due to slow loading and large size of FieldLayoutItems. JIRA loads elements into fieldLayoutCache by FIELDLAYOUT and at the same time load all related rows from FieldLayoutItem table.
See related ticket for context JRASERVER-66013.
Since fieldLayoutCache is used in many places, slow population will cause performance problems, see for example: JRASERVER-29310 and JRASERVER-61166.
Environment
- Large number of rows in fieldlayoutitem table - 200k+:
select count(1) from fieldlayoutitem; 1355666
Expected Results
Population of fieldLayoutCache is fast
Actual Results
Population of fieldLayoutCache is slow.
Note
- SQL logs will have the following:
SELECT ID, FIELDLAYOUT, FIELDIDENTIFIER, DESCRIPTION, VERTICALPOSITION, ISHIDDEN, ISREQUIRED, RENDERERTYPE FROM public.fieldlayoutitem WHERE FIELDLAYOUT='10100'"
- Stack-trace of the long running thread will be similar to this:
... at com.atlassian.jira.issue.fields.layout.field.AbstractFieldLayoutManager.getRelevantFieldLayout(AbstractFieldLayoutManager.java:264) at com.atlassian.jira.issue.fields.layout.field.DefaultFieldLayoutManager.getFieldLayout(DefaultFieldLayoutManager.java:702) at com.atlassian.jira.issue.fields.layout.field.DefaultFieldLayoutManager.getUniqueFieldLayouts(DefaultFieldLayoutManager.java:586) at com.atlassian.jira.issue.fields.layout.field.DefaultFieldLayoutManager.getUniqueFieldLayouts(DefaultFieldLayoutManager.java:562) at com.atlassian.jira.issue.fields.DefaultFieldManager.findVisibleFieldLayouts(DefaultFieldManager.java:503) at com.atlassian.jira.issue.fields.DefaultFieldManager.getUniqueSchemes(DefaultFieldManager.java:419) ...
- Other action might also flush fieldLayoutCache, some examples (not limited to that):
- Add issue type - /secure/admin/AddIssueType.jspa
- Remove issue type - /secure/admin/DeleteIssueType.jspa
- Add issue type scheme - /secure/admin/ConfigureOptionSchemes.jspa
- Remove issue type scheme - /secure/admin/DeleteOptionScheme.jspa
Attachments
Issue Links
- causes
-
JRASERVER-29310 Filter gadgets take several minutes to load after a field configuration context change
-
- Closed
-
-
JRASERVER-61166 Performance of JIRA Datacenter degrades significantly after customfields configuration task
-
- Gathering Impact
-
-
PSR-203 Loading...
- is cloned from
-
JRASERVER-66013 JIRA inefficiently populates fieldLayoutCache due to slow loading of FieldLayoutItems
-
- Closed
-
- is related to
-
JRASERVER-70233 Performance degradation of create project with per context fields configuration
-
- Closed
-
-
JRASERVER-61704 Slow loading of Project - Fields screen
-
- Gathering Impact
-
- relates to
-
JRASERVER-69446 Removing actor from project role can make Jira unresponsive
-
- Closed
-
-
JSWSERVER-20618 Performance of Jira can degrade significantly due to slow sprint cache population
-
- Closed
-
-
JRASERVER-68647 After successfully deleting custom fields on Jira Data Center some operations may result on NullPointerException on some nodes of the cluster
-
- Gathering Impact
-
-
JRASERVER-67279 Request timeout when creating project
-
- Long Term Backlog
-
-
JRASERVER-63501 Better scaling of Custom Fields and Field Configurations
- Gathering Interest
- is mentioned by
-
CFC-6 Loading...
- Mentioned in
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...