If I go into a Project and then click on the tasks my browser just freaks out and hangs for 3-4 minutes. The CPU consumption jumps to 100% and the memory usage goes up to around 50% or 1GB or so. I don't have a huge amount of tasks to load, maybe 10-12 spread out over a 2 months period but loading the chart at the bottom generated by jsgant cripples the entire browser. After it loads if I try to scroll right in the chart frame it again spikes the cpu usage up to 100% and the whole browser hangs for 5-10 seconds.
Now I'm not sure if this is only a JSGantt problem or a combination of it being used inside of Storm. Either way I'm running Firefox 3.63 in Ubuntu 10.04
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | image001.png | 132.93 KB | cfelce |
Comments
Comment #1
juliangb commentedWe´ve bundled JSGantt with storm, so if it is a problem with the library, it should affect all users the same way.
Haven´t heard of this issue before so unsure.
Does this happen with all Gantt Chart views? What happens if there are fewer tasks? Can you view the page on anther computer / browser?
Needs more info based on those 3 questions...
Comment #2
cfelce commentedHi,
I have the same issue for the version 6.x-1.33,
I have put the the image as an attachment.
Comment #3
juliangb commentedThanks for the post. What browser / os / php versions etc are you using?
Also the questions from #1...
Comment #4
danepowell commentedI'm seeing the same thing, Firefox 3 on Windows 7. This is a "known" issue with jsGantt I think... ("known" to its users anyway- the maintainer seems to be AWOL)
http://code.google.com/p/jsgantt/issues/detail?id=30
Comment #5
juliangb commentedOK, the way to solve this is ideally to try to get the fix applied to the upstream library (jsGantt), but if the maintainer is AWOL then we can simply apply the fix to the version in Storm.
We need a patch for this.
Comment #6
danepowell commentedIt sounds like from that issue that a good start would be to convert as much of the table/tr/td code to divs as possible.
By the way, I strongly suggest/request that you use the modified version of jsGantt in my module (views_jsgantt) as a starting point for optimization, since it already incorporates a number of bug fixes and enhancements over the latest jsGantt release.
Comment #7
juliangb commented@Dane Powell,
Happy to move over to using views_jsgantt for gantt charts. It just needs someone to write a patch.
Has this issue already been solved in views_jsgantt?
Comment #8
danepowell commentedNo, I have not addressed any performance issues, just some formatting issues (trying to make things display better in certain themes, increase CSS compliance/reliance, etc).
Comment #9
juliangb commentedComment #10
juliangb commentedComment #11
danepowell commentedJust FYI, jsGantt (the library) seems to be completely abandoned by the maintainers. I'm thinking of writing a wrapper module for dhtmlxGantt instead of jsGantt, but I need to find sponsorship for this. I also welcome suggestions for alternative Gantt libraries to use.
Comment #12
juliangb commentedThanks, that's useful information (although I have suspected it for a while).
Would the wrapper be similar to your jsGantt views module?
I'd be keen to utilise a views plugin rather than hardcoding integration for a specific Gantt library as was previously with jsGantt.
There is a list of alternative Gantt solutions at #701286: Refactor Gantt chart system that you may find helpful.
Comment #13
danepowell commentedYeah, my plan at this point would be to write another View plugin, exactly like views_jsgantt but with a different library on the backend.
Comment #14
juliangb commentedWon't fix this issue based on changing the Gantt chart support to a different library (non JsGantt) making this issue irrelevant.
Discussion for that to continue at #701286: Refactor Gantt chart system.