Hi
I've built an application which uses a majority of the Telerik SL controls, most significantly the Grid and Scheduler. Very quickly my application starts to use around 200mb of memory (Unmanaged according to ANTS) and this continues to grow, especially when using the Scheduler with Resource Grouping and switching Views.
I checked out the Team Pulse online demo to see what sort of memory consumption that has and was very surprised to see that grow to 300mb within minutes of poking around.
I've also tried some to the Telerik competitors online demos and they seem to suffer the same issues, with the Devexpress grid demos consuming 350-400 mb after a couple of minutes.
Anyway I guess what I want to know from my fellow developers is "how much is too much". In this day and age of 4Gb as standard on a laptop am I being too sensitive, or should I drop SL as a platform and go back to ASP.Net?
Thanks
Derek
I've built an application which uses a majority of the Telerik SL controls, most significantly the Grid and Scheduler. Very quickly my application starts to use around 200mb of memory (Unmanaged according to ANTS) and this continues to grow, especially when using the Scheduler with Resource Grouping and switching Views.
I checked out the Team Pulse online demo to see what sort of memory consumption that has and was very surprised to see that grow to 300mb within minutes of poking around.
I've also tried some to the Telerik competitors online demos and they seem to suffer the same issues, with the Devexpress grid demos consuming 350-400 mb after a couple of minutes.
Anyway I guess what I want to know from my fellow developers is "how much is too much". In this day and age of 4Gb as standard on a laptop am I being too sensitive, or should I drop SL as a platform and go back to ASP.Net?
Thanks
Derek
1 Answer, 1 is accepted
0
Hello Derek,
I found a problem with RadScheduler examples. Most of them are using static data as a source which lead to memory leak. Even when using weak event pattern if data is static - it will never be collected and because of that RadScheduler will also stay in memory.
We will fix it for 2011 Q1 release.
Thank you for reporting it. I have updated your telerik points.
Greetings,
Hristo
the Telerik team
I found a problem with RadScheduler examples. Most of them are using static data as a source which lead to memory leak. Even when using weak event pattern if data is static - it will never be collected and because of that RadScheduler will also stay in memory.
We will fix it for 2011 Q1 release.
Thank you for reporting it. I have updated your telerik points.
Greetings,
Hristo
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!