Comments on: Analyze a slow asp.net web page, tale of

By: cna training

cna training — Wed, 10 Mar 2010 19:35:18 +0000

nice post. thanks.

By: alkampfer

alkampfer — Fri, 19 Dec 2008 13:49:20 +0000

Client script pagination is the best approach, but you should avoid including all the data in the page.
The best approach is doing pagination asking new data to the server via ajax calls and json serialization.
Check out flexigrid for jquery to look at a real example.

If you really need instant response, you can follow this pattern
1) render the page with the first page
2) immediately begin to ask for next pages
3) if the user paginate to a next page check if it is already loaded, if yes render it, if not download and render.
With this approach the time needed to show the first page is slow, and you can download remaining data while user is reading the page.

With jquery dom manipulation is quite simple, and doing a similar approach should be quite simple.

Another approach in aspx is creating an aspx page that only renders the grid, then enable server side caching, and use partial page rendering with jquery (when the user press pagination button you call the page that renders the grid and substitute all html into the div of the original grid).

Alk.

By: Dario Santarelli

Dario Santarelli — Fri, 19 Dec 2008 11:14:37 +0000

In my experience I’ve often found scenarios where developers prefer to populate a generic Data Control with a great deal of records, then manage pagination by client-side scripts.
According to this approach, page size and load latency can be very heavy but once data is loaded, pagination is immediate.

What do you think about this kind of scenario considering to load a reasonable number of records?

P.s.: I agree with you: Server-side pagination + Caching is always a good practice