Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-1164

Generation of charts with greater than a couple hundred issues is slow

XMLWordPrintable

        Form Name

          [JSWSERVER-1164] Generation of charts with greater than a couple hundred issues is slow

          Alex Hennecke (Inactive) added a comment -

          The computed data the Hour Burndown Chart is based on is now cached in memory.

          Alex Hennecke (Inactive) added a comment - The computed data the Hour Burndown Chart is based on is now cached in memory.

          JC added a comment -

          Awesome Tom.

          Note that the enhancements are in 4.1
          Will be awaiting for your results.

          PS: apologies for misspelling your name in my previous message.

          Cheers,
          JC

          JC added a comment - Awesome Tom. Note that the enhancements are in 4.1 Will be awaiting for your results. PS: apologies for misspelling your name in my previous message. Cheers, JC

          Tom Griffin added a comment -

          I will take a look at it. We are installing 4.0 on test systems now to validate overall performance improvements.

          Tom

          Tom Griffin added a comment - I will take a look at it. We are installing 4.0 on test systems now to validate overall performance improvements. Tom

          JC added a comment -

          Tim,

          GH 4.1 should ameliorate the chart rendering time.
          Can you let me know if you see any improvements on this?
          4.1 will be release the 2nd of November.

          Since we need to parse all issue histories to compute the charts, the next step would be take advantage of the JQL support of the History and Worklogs when it will be implemented.

          I will transfer this is the blocked issues until the JQL gets enhanced.

          Cheers,
          JC

          JC added a comment - Tim, GH 4.1 should ameliorate the chart rendering time. Can you let me know if you see any improvements on this? 4.1 will be release the 2nd of November. Since we need to parse all issue histories to compute the charts, the next step would be take advantage of the JQL support of the History and Worklogs when it will be implemented. I will transfer this is the blocked issues until the JQL gets enhanced. Cheers, JC

          JC added a comment -

          Have you tried to create a context that is Sorted by Issue keys (much faster then other sorters).

          that should speed up your Chart generations.

          Let me know.

          Cheers,

          JC added a comment - Have you tried to create a context that is Sorted by Issue keys (much faster then other sorters). that should speed up your Chart generations. Let me know. Cheers,

            ahennecke Alex Hennecke (Inactive)
            fdb0f63b609d Tom Griffin
            Affected customers:
            1 This affects my team
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: