Web Services
Top achievements
Rank 2
Rank 2
Web Services
asked on 20 Aug 2013, 07:20 PM
I read through your caching example and I just have a couple quick questions. Can I set the amount of time that the cache refreshes, or is it static, or based on the session timeout or something. Also, does this cache it so if I had a grid on page 1, then went to page 2, then back to page 1, it still pulls the cached version?
Here's my problem. I have a gird with a large amount of data that is relatively statice. I want the page to be able to load super fast (I get it'll have to pull the data once) so I'm trying to do everything I can to make this page load as fast as I can.
Here's my problem. I have a gird with a large amount of data that is relatively statice. I want the page to be able to load super fast (I get it'll have to pull the data once) so I'm trying to do everything I can to make this page load as fast as I can.
3 Answers, 1 is accepted
0
Hi,
The client side caching is static, this means that all items will be removed from the cache when the page is unloaded. Also all items that are shown into the grid are cached. So if you load initially the first page all items are cached, then when user navigates to the second page a request to the web service is perfumed and new data is loaded into the RadGrid. At this point the items for the second page are put into the cache. If the user returns to the first page the items will be got from the cache and there are not any requests to the web service. You can observe this behavior on our demo by inspecting it with firebug or fiddler.
However please note that the client side binding is fast only with small number of grid items. If you tried to load for example 10 000 records without paging the execution of javascript for creating these items can slow down the page.
I hope this helps.
Regards,
Radoslav
Telerik
The client side caching is static, this means that all items will be removed from the cache when the page is unloaded. Also all items that are shown into the grid are cached. So if you load initially the first page all items are cached, then when user navigates to the second page a request to the web service is perfumed and new data is loaded into the RadGrid. At this point the items for the second page are put into the cache. If the user returns to the first page the items will be got from the cache and there are not any requests to the web service. You can observe this behavior on our demo by inspecting it with firebug or fiddler.
However please note that the client side binding is fast only with small number of grid items. If you tried to load for example 10 000 records without paging the execution of javascript for creating these items can slow down the page.
I hope this helps.
Regards,
Radoslav
Telerik
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed now.
0
Web Services
Top achievements
Rank 2
Rank 2
answered on 23 Aug 2013, 12:52 PM
I have around 300 records and it probably won't grow too fast. Would you recommend caching then? What is the fastest way to load this data and display it? I have filters at the top as well. The client that I'm building this for literally complains if there's like a 3 second delay on anything. How would you recommend going about displaying and loading this data the fastest?
0
Princy
Top achievements
Rank 2
Rank 2
answered on 23 Aug 2013, 02:08 PM
Hi,
Please have a look at this documentation on Client/server grid performance optimizations to load the data fast.
You can also try Custom Paging which helps to fetch only a fixed number of records and perform operations on this limited set of data.
Then another approach is Virtual Scrolling/Paging when you have large sets of data.
Hope this helps.
Thanks,
Princy
Please have a look at this documentation on Client/server grid performance optimizations to load the data fast.
You can also try Custom Paging which helps to fetch only a fixed number of records and perform operations on this limited set of data.
Then another approach is Virtual Scrolling/Paging when you have large sets of data.
Hope this helps.
Thanks,
Princy