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

Dashboards with a large amount of gadgets cause performance degradation in high concurrent access environments

      Many gadgets on one dashboard may lead to performance problems in a high traffic / concurrent access scenario.

      It becomes worse when those gadgets require expensive searches and post processing.

      Reproduction Steps

      1. To make things easier please use slowmo for such url:

      /plugins/servlet/gadgets/ifr

      and give it 60 seconds delay.

      2. Create dashboard with 8 gadgets

      3. In server.xml change maxThreads to 8 and restart jira

      4. Open dashboard page in one tab and then in another. Dashboard should not load in second one before all gadgets finish loading in first one.

      Warning, over-communication: no one would want to change maxThreads to 8 on production environment, but this is example configuration to makie it easier to reproduce. On production environment you would get x10 more threads but also x100 more concurrent users and that's when this problem pops up.

      Rendering gadgets which are not visible also means a huge footprint for OD.

      Suggested solution:

      Do not initialize gadgets which are not visible on user screen. Initialize them once they become visible.

            [JRASERVER-37754] Dashboards with a large amount of gadgets cause performance degradation in high concurrent access environments

            There are no comments yet on this issue.

              Unassigned Unassigned
              gtanczyk Grzegorz Tanczyk (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated: