We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-45903

Bad performance noticed on issues with long history

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Platform Cloud'
            1. Jira Platform Cloud
            2. JRACLOUD-45903

            Bad performance noticed on issues with long history

            XMLWordPrintable

              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                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

                        jgeeves geeves
                        rrosa@atlassian.com Rodrigo Rosa
                        Votes:
                        24 Vote for this issue
                        Watchers:
                        35 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            jgeeves geeves
                            rrosa@atlassian.com Rodrigo Rosa
                            Votes:
                            24 Vote for this issue
                            Watchers:
                            35 Start watching this issue

                              Created:
                              Updated:
                              Resolved: