Home/ Questions/Q 8462957
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T14:19:36+00:00

I have a listview with 250 rows and 4 columns in my ASP.Net 4.0/C#

  • 0

I have a listview with 250 rows and 4 columns in my ASP.Net 4.0/C# application. The Rendered page size (from Trace) is 650,000 Bytes. The entire listview is in an update panel.

The listview facilitates view/add/edit/delete operations on the listview records.

Every POSTBACK action (i.e. edit click, delete click) causes a POSTBACK request of size 112,000 Bytes and an AJAX Response of ~650,000 Bytes.

The listview gets the data from a declarative data source (SQLDataSource) on the page. And the listview is bound on each round trip.

I want to reduce the data going back and forth in every call because on a slow connection, these AJAX calls take 2-3 minutes to complete.

What I have tried –
Removed the update panel over the entire listview and added an update panel over each:

  • ItemTemplate contents
  • AlternateItem Template contents
  • Edit Template contents
  • Insert Template contents

I was hoping that with the template in each row, it would reduce the size of the AJAX response since only the HTML for the update panel would come back. Unfortunately, it does not seem to work that way.

Any inputs on how the problem in my case can be solved?

Thanks in advance for looking this up.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The problem with an UpdatePanel is that you are not using real AJAX. Instead ASP.NET uses some really clever hacks to create the illusion of a partial page update. On the background, your whole page life cycle is executed. This also means that your complete ViewState is send back and forth.

    If you want a faster experience, you should not use UpdatePanels. Instead, use plain HTML controls (preferably not even server controls) and use JavaScript and a server side webservice (such as WebAPI or a WCF service) to respond to the client side requests.

    Those requests and response will only contain some JSON data and no markup. Your data can be kept to a minimum. If for example, a user removes a row, you only have to send the Id of the row to your service and it will return success or failure. The client will use JavaScript and maybe something like KnockoutJS to render the result. This will give you minimal overhead and a better performance.

    • 0