Slow response to page-change requests with the list_navigation webblock

Slow response to page-change requests with the list_navigation webblock

  
Hello,

We have an application which displays a few (4 - 6) records at a time from a very large dataset (app. 10,000 records).  Whenever we invoke a page change using the list_navigation RickWidget, there is a huge amount of what appears to be viewstate data being posted back, cauing the response to be very sluggish. Many of our users are 'tethered' onto the web via a 3G device, and data payload size is especially critical for them.  Is there some way to improve this performance?  I discovered that an Ajax call made directly to the refreshPage action is relatively fast, but any which comes through the list_navigation control is almost prohibitively slow.  I had considered replacing the control with a custom-made paging control using an ajax call, but would rather use this one if possible.

Chuck Doherty



We resolved this issue.  The problem turned out to be caused by a huge amount of page viewstate data which was added by having a "Export to Excel" option on the page.  This widget, by even being present, dramatically enlarged the viewstate of any page which had a large dataset associated with it.  Removing it from ours made SUCH a dramatic performance improvement (by orders of magnitude) that it may be worth your while to review your applications for any pages which feature the Export to Excel option and review the size of the page's viewstate.  If you don't really need the export function (which is added to many pages by default), you can gain a big performance improvement by removing it.  We are finding that it is rarely needed anyway, and we almost always remove it as a matter of course.

We changed the Export option into a link to a popup which contains a similar query to the main page, and everything is working great now.

Chuck Doherty