If the CurrentTimeMarker is enabled (it is by default), the resources are grouped, and events with different resource values (about 70) are loaded for the current day, a significant performance deterioration is observed.
With the CurrentTimeMaker disabled or the events loaded for a date different than today (past or future) the performance issue is not exhibited.
No exceptions are thrown, but the Scheduler becomes unresponsive.
There should be no performance hit, regardless of CurrentTimeMarker being enabled/disabled.
Regression introduced in R2 2018.
The mobile mode of the Scheduler must be turned off.
Reproducible in the demos.
The moveStart event does not fire and the event cannot be moved.
The moveStart event fires and the event can be moved.