I am using fullcalendar and I really like it! I am developing a simple application which needs to show a calendar able to rendere lots of events every day/week but I am facing an issue, since the pure web HTML/JS application runs in an embedded device with a chromium-based browser when I inject the events (let's say 1000 in a week in the week view) it tooks a lot of time, doesn't matter if I do it by .addEvent or .addEventSource, I also tried to put them inside a .batchrendering callback but no luck.. Then I tried to load them using the "events (as a function)" way but still it is slow.
The events data is retrieved by my AJAX callbacks in a centralized way thus I cannot use "events (as a JSON feed)" method.
The strange thing that I noticed is that the successCallback or the .addEventSource call returns after some reasonable time but then, the system, remains blocked for a lot of time, if I try to inspect the HTML I can see that the generated elements are destroyed and created again for a lot of time keeping my cpu at 100%
Is it a known issue or am I doing something very wrong? Which should be the fastest way to insert the elements?
Note: I am using the fullcalendar v4, could be v5 a more powerful alternative?
Thanks :)
question from:https://stackoverflow.com/questions/66067908/fullcalendar-bad-performance-and-continuous-box-destroy-create
