We have around 500 events loaded in a month, and having unnecessary data manipulation in between actions (change views, selected date,...) seems to be really costly.
Can't really understand how and if the scheduler caches the data, but we would need to have something like the CacheAdaptor, which will not load already loaded data. We get an error when we use the CacheAdaptor, taking in account that it isn't included in your new docs I assume it's still not for regular use.
We are using the UrlAdaptor now.
Another approach we tried is with local data, and although we have full control of the requests to the server (we can do local caching and not send unneeded requests), manipulating the events with scheduleObj.addEvent, scheduleObj.deleteEvent and scheduleObj.saveEvent is much much slower than leaving that problem to the scheduler's data manager.
Also, the schedule obviously freezes the window when these tasks take a long time to process and not sure if there's any async way of doing that.
So, my question is how to improve the schedule's speed when working with a lot of events?