Hello
I have a scheduler for doctors to set appointments for their patients and the performance is really slow. I found out the issue with my scheduler is the amount of resources I have. I have 4 different resources. (Patient, Physician, Facility, and Appointment Type). The patient record is around 3000 records and it seems to be the culprit here. When I take it out the page size is reduced by half. It takes about 6 seconds to go from one week to another week and without the patient information it takes 3 seconds. So still quite a lot
What steps can I take to fix this? Alternatives and such
Thanks :)
I have a scheduler for doctors to set appointments for their patients and the performance is really slow. I found out the issue with my scheduler is the amount of resources I have. I have 4 different resources. (Patient, Physician, Facility, and Appointment Type). The patient record is around 3000 records and it seems to be the culprit here. When I take it out the page size is reduced by half. It takes about 6 seconds to go from one week to another week and without the patient information it takes 3 seconds. So still quite a lot
What steps can I take to fix this? Alternatives and such
Thanks :)
2 Answers, 1 is accepted
0
Ekjot
Top achievements
Rank 1
Rank 1
answered on 12 Jul 2013, 06:40 PM
Any tips guys? Any help would be greatly appreciated. Thanks :)
0
Shinu
Top achievements
Rank 2
Rank 2
answered on 14 Jul 2013, 05:24 AM
Hi Ekjot,
The number of resources slows down the rendering and overall performance considerably which has to be expected. I am not sure whether you are using the latest version of RadControls. In the previous releases the images to support the appointment rounded corners (and the predefined resources) were quite large. For example in the Q1 2010 release, the appointment sprite itself is taking 25MB memory when loaded. Add 5 resources to the fray and you have 150MB memory down with a single blow.
As far as I know there isn't anything particular that you can do with RadScheduler. Still you can review the optimization techniques as shown in this demo. Another suggestion is Client side binding using web services can give you excellent performance in most common cases as shown here.
Apart from this some general performance tips you can incorporate such as using RadScriptManager and RadStyleSheetManager to optimize output as well as page load time as described here. Also you can read more about the general performance tips from here Link1, Link2.
Thanks,
Shinu.
The number of resources slows down the rendering and overall performance considerably which has to be expected. I am not sure whether you are using the latest version of RadControls. In the previous releases the images to support the appointment rounded corners (and the predefined resources) were quite large. For example in the Q1 2010 release, the appointment sprite itself is taking 25MB memory when loaded. Add 5 resources to the fray and you have 150MB memory down with a single blow.
As far as I know there isn't anything particular that you can do with RadScheduler. Still you can review the optimization techniques as shown in this demo. Another suggestion is Client side binding using web services can give you excellent performance in most common cases as shown here.
Apart from this some general performance tips you can incorporate such as using RadScriptManager and RadStyleSheetManager to optimize output as well as page load time as described here. Also you can read more about the general performance tips from here Link1, Link2.
Thanks,
Shinu.