we do have around 20000 tasks with around 20 root tasks (the others somehow children). When we delete on root object having not any children via applyChangeset, changes.removed it takes even on brand new M1 MacBook around 40 seconds until the gantt is usable (no sorters applied ...).
The same if we do an interactive delete with your standard delete context option
unfortunately your big data set demo does not show this kind of behavior. Could it be influenced by the amount of data we have in one record, current data are like see attachments.
Measures:
initially store data to store (around 20000 tasks), around 3 seconds
Could you please attach data JSON we could use to reproduce the issue, together with instructions what exactly should be done to have this lag?
As I understood, you didn't remove a task with context menu, but apply changeset that removes some task with 99 subtasks?
Hi, the long time occurs on deleting/adding (even a task without any sub structure) via UI or via applyChanges. So if you use the attached test data you could just try to delete one of the (PR) objects on top level without a sub structure
added also the dependencies
Could you please share your TaskModel too, I see you used different field names for task model. So, I need to know if you used mapping for startDate -> scheduledStartDate, and so on for endData. I see it equals to "-1" which is not correct date.
by the way the same situation is with adding an object. Just as an info (I'm sure that you are anyway working on that with high priority), this problem currently delays our system rollout at one of our biggest customers
Last edited by pincherhgz on Fri Feb 03, 2023 3:56 pm, edited 1 time in total.