Support Forum

Our code is distributed as ES202x sources. If you need the ES5 code you will need to setup the transpilation pipeline yourself.

The optimizations I made were just merged - should appear in the tomorrow nightly or in the 5.5.2 release. They improve the performance of refreshWbs method and also avoid calling it at all for simple (non-structural) changes like description field. https://github.com/bryntum/support/issues/7320

Ok, thanks for the update. It seems to generally match my benchmarking. I'll investigate if something can be improved.

Hm.. perhaps it was added after 5.5.0 - try with 5.5.1?

Can you please test the performance w/o filtering but with sorting? I'm benchmarking on the reduced dataset, so numbers are different, I'm curious if the behavior in your app is matching.

Should still exists - its a publich method https://bryntum.com/products/gantt/docs/api/Scheduler/crud/AbstractCrudManagerMixin#function-suspendChangeTracking. Crudmanager as a mixin is added to the Project class.

Hm.. I definitely see 1 filter enabled in your app:

Some further checks revealed that its actually filtering that impacts the performance most, not sorting. My benchmarking for applyChangeset:

Raw: _3ms
Sorting: _8ms
Filtering: _157ms
Sorting + Filtering: _134ms

Does it match with your experience?

Thanks for the update, I've created a ticket to investigate: https://github.com/bryntum/support/issues/7320

Ok, those messages seems to trigger excessive data updates. Perhaps if that can be fixed, even performance with sorter will be acceptable (theoretically should be the same as applying sort manually as you tried).