-
Suggestion
-
Resolution: Tracked Elsewhere
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Performing some testing with JIRA 6.4.5, I've noticed that there is a huge difference when logging work on an issue with no history and on an issue with a long history.
I enabled Profiling on JIRA to check the difference:
Example 1: Issue with 858 entries on history:
2015-10-21 15:18:53,596 http-bio-8080-exec-21 DEBUG sysadmin 918x163x1 1zsbpp 0:0:0:0:0:0:0:1 /secure/CreateWorklog.jspa [atlassian.util.profiling.UtilTimerStack] [6104ms] - /secure/CreateWorklog.jspa [0ms] - PermissionManager.hasPermission() [6100ms] - CreateWorklog.execute() [1ms] - PermissionManager.hasPermission() [1ms] - PermissionManager.hasPermission() [0ms] - PermissionManager.hasPermission() [0ms] - PermissionManager.hasPermission() [0ms] - PermissionManager.hasPermission() [0ms] - PermissionManager.hasPermission() [44ms] - IssueIndexManager.reIndexIssueObjects() [1ms] - PermissionManager.hasPermission() [11ms] - IssueIndexManager.reIndexWorklogs()
Example 2: Issue with 4 entries on history:
2015-10-21 15:21:44,662 http-bio-8080-exec-24 DEBUG sysadmin 921x169x1 1zsbpp 0:0:0:0:0:0:0:1 /secure/CreateWorklog.jspa [atlassian.util.profiling.UtilTimerStack] [189ms] - /secure/CreateWorklog.jspa [0ms] - PermissionManager.hasPermission() [186ms] - CreateWorklog.execute() [0ms] - PermissionManager.hasPermission() [0ms] - PermissionManager.hasPermission() [0ms] - PermissionManager.hasPermission() [0ms] - PermissionManager.hasPermission() [0ms] - PermissionManager.hasPermission() [0ms] - PermissionManager.hasPermission() [37ms] - IssueIndexManager.reIndexIssueObjects() [0ms] - PermissionManager.hasPermission() [9ms] - IssueIndexManager.reIndexWorklogs() [1ms] - PermissionManager.getProjects()
Notes
It further degrade the performance of the instance and it takes longer to load issues with large history items
- is related to
-
JRASERVER-45903 Adding a new worklog entry is slow due to a large change history
- Long Term Backlog
- relates to
-
JRACLOUD-60107 A large change history or worklog on an issue can cause an OOME when displaying the History tab
- Closed
-
JRACLOUD-64001 Limit results in work log tab
- Closed