Hi there,
I have started having a slow loading issue with the schedule that I am showing up to 300 items on it and it literally takes less than a sec from the database.
I am having a dynamic sql statement rather than using the data access layer or entity framework for this particular approach.
In addition, I am having some resources on it, and an advanced form for a popup wise.
What could be the start point for me to check the issue out?
Cheers!
6 Answers, 1 is accepted
Please refer to the following online documentation outlining the common techniques to optimize the performance of our controls. There is a paragraph with specific tips for the RadScheduler control.
Regards,
Dimitar Terziev
Telerik

Hi Dimitar,
Thanks for the reply.
I understand that there is a general knowledge in regards to ASP.NET AJAX, however, I do not think we have done any extreme or different structure than the usual. It is more about how to use the scheduler control in a most effective way. I am happy to provide the code (front end - back end) and find out whether anything has been done against the suggested structure. It is a big concern for us at the moment and I cannot create a ticket, unfortunately.
I would appreciate if you can give a help, thank you.
The general approch to improve the performance is to use WebService binding, which will reduce the html transferred from the server, since the scheduler appointments are rendered on the client in such a case.
Regards,
Dimitar Terziev
Telerik

Hi,
Yes we do use the WebService binding.
In addition that, here is the scheduler structure that may give you an idea how it is built.
Per our performance test, the sql query takes less than a sec and all begin with binding the entity class and transferring through the web interface.
01.
<
telerik:RadScheduler
runat
=
"server"
ID
=
"RadScheduler1"
EnableRecurrenceSupport
=
"false"
OnClientAppointmentEditing
=
"AppointmentEditing"
OnClientAppointmentInserting
=
"AppointmentInserting"
OnClientAppointmentsPopulated
=
"OnClientAppointmentsPopulated"
02.
StartEditingInAdvancedForm
=
"false"
Skin
=
"Office2010Silver"
OnClientAppointmentCreated
=
"OnClientAppointmentCreated"
Height
=
"100%"
Width
=
"100%"
03.
EnableDescriptionField
=
"true"
OverflowBehavior
=
"Auto"
AppointmentStyleMode
=
"Default"
OnClientAppointmentDataBound
=
"OnClientAppointmentDataBound"
CustomAttributeNames
=
"StaffID,JobStatusID,ClientID,Address,ContactNumber,Suburb,State,Postcode,StaffName,JobStatusName,ClientName,JobTitle,JobColor,JobCustomerRefNo"
04.
Localization-AdvancedDescription
=
"Job Comment"
DataDescriptionField
=
"Description"
StartInsertingInAdvancedForm
=
"false"
Localization-ConfirmDeleteTitle
=
"Cancel job"
Localization-ConfirmDeleteText
=
"Are you sure to cancel the selected job ?"
Localization-ContextMenuAddAppointment
=
"Add Job"
MonthView-VisibleAppointmentsPerDay
=
"10"
05.
SelectedView
=
"WeekView"
TimelineView-UserSelectable
=
"false"
OnClientNavigationCommand
=
"OnClientNavigationCommand"
DayStartTime
=
"06:00"
DayEndTime
=
"19:00"
06.
FirstDayOfWeek
=
"Monday"
LastDayOfWeek
=
"Sunday"
DayView-HeaderDateFormat
=
"dddd, MMMM dd, yyyy"
MonthView-HeaderDateFormat
=
"MMMM, yyyy"
AllowDelete
=
"false"
>
07.
<
WeekView
HeaderDateFormat
=
"dddd d, MMM "
ColumnHeaderDateFormat
=
"dddd, MMMM d"
/>
08.
<
WebServiceSettings
Path
=
"Schedule/SchedulerWebService.asmx"
ResourcePopulationMode
=
"ServerSide"
>
09.
</
WebServiceSettings
>
10.
<
TimeSlotContextMenuSettings
EnableDefault
=
"false"
></
TimeSlotContextMenuSettings
>
11.
<
AppointmentContextMenuSettings
EnableDefault
=
"false"
></
AppointmentContextMenuSettings
>
12.
<
ExportSettings
>
13.
<
Pdf
PageTopMargin
=
"1in"
PageBottomMargin
=
"1in"
PageLeftMargin
=
"1in"
PageRightMargin
=
"1in"
></
Pdf
>
14.
</
ExportSettings
>
15.
</
telerik:RadScheduler
>

Could you please try to reproduce the slow load you have experienced in the sample project attached to this reply? If you manage to do so you can open a support ticket and attach it back for further review. If it is more convenient to you, you can attach another runnable sample that demonstrates the issue and our guidelines should be helpful in isolating the problem.
Regards,
Ivan Danchev
Telerik