Geeks With Blogs
CodeSeeker Just another developer trying to do the right thing
There are many areas where optimization may occur, and the resulting solution may be different for different areas of concern. In an ASP.NET application, delay may occur in the following places:
  1. On the client (within Javascript)
  2. Along the network between the client and the web server (lots of information on the page getting submitted, in ViewState or otherwise)
  3. On the web server during processing and/or rendering
  4. On any other application servers during processing
  5. Along the network between the web/app server(s) and the database server(s)
  6. On the database server(s) during query execution (including stored procedures, user-defined functions, etc).
For example, because a significant portion of our userbase is in a remote office with limited bandwidth, we found that it was most important for our application to optimize the time between the client and the web server. So even though it would have saved trips to the database (a common optimization technique), we took some stuff out of ViewState and are making additional database calls to retrieve it.

When attempting to make a decision between conflicting ASP.NET application optimization solutions, the area of concern must first be defined. Otherwise, you may be optimizing an already-sufficiently optimal subsystem. Posted on Monday, July 28, 2008 4:41 PM | Back to top

Copyright © Mike Ellis | Powered by: