I'm working with a data set that is about 5,000+ parent nodes and a handful of rollup children per parent node, equating to around 20,000 total entries, although the rollups are only displayed on the timeline and not in the grid.
After passing this object to the Gantt component, there is up to a minute of loading time before the component renders. Also, sometimes the lazy load scrolling will freeze up the component for a few seconds if you scroll quickly. I'm wondering what opportunities are available to optimize the load times and performance.
One thing we are looking into currently is to load the data into the component in chunks, or loading the grid data first and then timeline data afterwards. Any information would be highly appreciated!
Last edited by jayoung@copado.com on Thu Oct 21, 2021 8:46 pm, edited 3 times in total.
I tried to use your data to test it in our basic React demo but it was always only a couple of seconds w/o any freezes. Would you please post the complete application so that we can investigate all aspects of performance?
If you change the big data set example to 30000+ you can see the time starts to really increase. We have closer to that many entries. In general, what can be done to make the loading or calculation faster? I found the ProjectModel setCalculations function which seems like it would help, but I get a function not found when I attempt to use it. Tried this method also, didn't seem to impact.
Any advice about best practices for very large sets would be highly appreciated. Loading in chunks freezes the component until they load fully so it doesn't really improve performance
Provide please any additional data you can: steps to do with our demo(s), values used for testing, measured time(s), configuration of the Gantt, data used for testing, etc. Post it here or in the ticket itself.
That's interesting to see that perspective... That same example takes at least 30 seconds to load on my machine. In our cloud hosted environments its 60 seconds or longer