Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-34028

/rest/api/2/status REST request performance

    XMLWordPrintable

Details

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Fire a REST request /rest/api/2/status to the JIRA instance would takes up a minimum of 1.5 minutes or sometimes even more than 2 mintues. It seems that JIRA is locating all the active status which associate to the workflow and workflow schemes.

      The problem seems to occur when you have a really large list of workflows and workflow schemes association. The request spending 99% of the time on waiting the request to be completed in order to retrieve 70++ statuses from the JIRA instance as we can see in the following screenshot:

      More result from JProfiler attached and a sample HAR file attached for further review.

      Attachments

        1. chrome_debug_tool.png
          chrome_debug_tool.png
          27 kB
        2. Jprofiler_CPI_Call_Tree.html.tar.gz
          254 kB
        3. jprofiler_cpu_part1.png
          jprofiler_cpu_part1.png
          69 kB
        4. jprofiler_cpu_part2.png
          jprofiler_cpu_part2.png
          84 kB
        5. localhost.har
          30 kB

        Issue Links

          Activity

            People

              edalgliesh Eric Dalgliesh
              yen@atlassian.com TeckEn (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: