When attempting to embed the Gannt Chart plugin in a Confluence page it hangs with the following:
2015-03-02_1638[1].png
This is similar to when using the gadget in JIRA where the time from adding the gadget to actually being able to interact with the gadget configuration is quite lengthy. It seems to be related to the number of issues in the JIRA instance judging by this part of the gadget UI:
2015-03-02_1641[1].png
How can we tune the plugin to be more responsive in large JIRA environments?
Using my latest version (download from my server at http://www.polscheit.de/plugins/jira/gantt-chart/gantt-3.1.9-JIRA6_2015-03-04T13-11-05Z.jar and install this JAR-file via "upload" button on JIRA's page "manage add-ons" as system admin.), I have optimized the performance of the Gantt Gadget.
Nevertheless, displaying such large amount of issue (> 200.000 issues) will always be an infrastructure problem: I assume, your database servers will never be fast enough retrieving all that data nor your LAN throughput from the server to your browser, which it may run into memory problems. Within JIRA's dashboard, the solution is to use a suitable filter (e.g. issues not being resolved or closed) in order to reduce the amount off issues. Idea behind the scene: nobody would like to scroll over >200.000 issues as this is not efficient working. Additional to use a suitable JIRA filter, you can specify a time period you are interested in. This can be "from" - "to" in form a absolute dates or even better by using relative dates (e.g. from '-4w' to '12w'). Having specified a time period based on relative dates, you'll get a time period automatically shifted per day. This would retrieve and display the issues belonging to that time period depending on "today" only, like one month in the past until 3 months within the future.
I appreciate your feedback.
Kind regards,
Frank
Hey Frank, We will update in our next window. The issue I see is that the gadget takes quite some time to load before we can specify a filter. this is true especially when embedded in Confluence. I will check how your optimizations affect this and let you know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We've updated to the latest version and set the default JQL to a query that will return 0 rows. We still see the gadget never finishes loading in Confluence yet loads instantly in JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Developing Gantt-Chart version 3.2, I have re-implemented issues' loading and parts of the internal issue container and have reached a performance boost: 1000 issues to be displayed within < 10 sec. using a common hosted virtual environment and within about 2 sec. using my optimized test environment based on server-side SSDs). May be, there's a bug avoiding the disable of the "loading" message in case of empty result set. Please have a look at your browser's console output. Kind regards, Frank
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is this what you need for Console output? Confluence gadget with console: http://screencast.com/t/HQUNcA5u6s Compared to the same gadget (same settings) in JIRA: http://screencast.com/t/86o2lsGNK7
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Frank Polscheit - Have you had a chance to look at the screencasts above?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am re-engineering the load algorithm to enhance performance, currently. Coming version 3.2 will be optimized to run 20x - 50x times or even faster (depending on your environment: loading e.g. 1000 issues between 2 - 10 sec.) according to my tests at the moment. Kind regards, Frank
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks. We will keep an eye out for it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.