[REACT] Out of Memory error when using Gantt + Resource Histogram

[tulioassis]

Hey!

The Gantt chart is loading correctly but when we add a Resource Histogram, the memory used by Google Chrome increases almost 4GB and then it gets crashed with out of memory error message.

Our project, for this test, has around 5k tasks, 4k dependencies, 9 resources and 4.5k assignments.

Do you know why the Resource Histogram consumes so much memory? Any tips to avoid it?

[arcady]

It basically calculates resource allocation for each resource per each tick (per each day in the demo..but that depends on the current zoom level it uses)
So on big datasets I guess it can take a lot of memory ..it's hard to tell more without seeing the code.
If you provide us with a test case we'll take a look what's going on.

[tulioassis]

Is there any possibility to provide the data already calculated to the histogram?

[arcady]

This can be done but you'll have to override some private code.
The histogram builds a special allocation report for each displayed resource row. Theoretically you can put there your own class instances that could implement some custom logic.

[tulioassis]

Thank you! Do you have any documentation about how override private code?

[marcio]

Hello tulioassis,

I'm afraid we don't have specific documentation regarding that, the closest thing would be this one https://www.bryntum.com/docs/gantt/api/guides#customization

[tulioassis]

Hey marcio,

we took a look and saw that the function calculateAllocation is taking some time to run, see this screenshot: https://ibb.co/jDR6TsK
We were only able to run it because we did it with 2200 tasks and 3 resources.

Do you know if Bryntum's team could take a look on it to see if it is a performance issue?

[mats]

If you could upload a simple test case (with dummy data) to us, that will let us investigate and do some profiling.

[tulioassis]

Sure! There is a dataset attached.

[tulioassis]

Please let us know if you're working on it or not then we can avoid duplicated effort.