Scheduler load time and responsiveness decrease with high volume of data

[Nithin]

In our application we have data for more than 200 rooms . We fetch data for all the rooms from the back end in one api call within a particular date range (10 or 15 days range) which can have large amount of data. If we bind all the data to the scheduler the rendering is very slow. Is there a way we could bind the data to the scheduler on scroll?

[Ivan Danchev]

Hello Nithin,

Currently loading events on scrolling (infinite scrolling or virtualization) the Scheduler's view is not implemented. This feature has been requested before: see this feature request in our Feedback Portal. At present it is not yet approved for implementation by the team so we would suggest voting for it. The highly demanded requests are usually planned with precedence for subsequent releases.

Regards,
Ivan Danchev
Progress Telerik

[Nithin]

Hi Ivan,
Is there a way to make binding the response JSON to scheduler a little more faster currently I'm using setDataSource() say something like getting the entire JSON and binding it in background without interfering with the user?

[Ivan Danchev]

Hello,

Binding to the response cannot be made faster, and most probably the rendering is what causes the slow down in your case. You could verify this by hiding the Scheduler with CSS initially:

.k-scheduler {
  display: none;
}

and showing it when it is bound to the data, in its dataBound event handler:

dataBound: function(e) {
  $(".k-scheduler").css("display", "block");
}

Dojo example.

Regards,
Ivan Danchev
Progress Telerik

[Nithin]

Hi Ivan,
I did manage to work a way around this slowness issue on render.
I have implemented a resource pagination through which only a small portion of large data set is displayed making the widget very fast in rendering.

resource pagination

PS: This is just my concept may have some bugs 

[Ivan Danchev]

Hi Nithin,

I am glad you have found a custom solution that avoids loading all resources at once. Thank you for sharing it. I hope it will be useful to other members of the community who face a similar scenario.

Regards,
Ivan Danchev
Progress Telerik