codebeater

General .NET, ASP.NET, C# and VB.NET discussion

About the author

Author Name is someone.
E-mail me Send mail

Recent comments

Authors

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2008

Lessons learned; debug="true"

Not too long ago I was working on a web app at my place of employment with several other people. It's a fairly complex app that makes heavy use (too much, IMO, but that's a different story) of AJAX. When we finally made this application available for beta testing our IT department was quick to point out that each request was causing over 1MB of bandwidth usage. After my initial shock my first impression was that the problem was being caused by the set of 3rd party tools we were using. However, a simple test using a page with intrinsic framework controls revealed that my suspicions were incorrect. It took many hours of frustration but eventually I noticed that debug in web.config was set to 'true'. Once I set it to false our bandwidth usage dropped to a very reasonable amount in the range of 12k to 75k, depending on the data being served. So, use my experience as a lesson and don't ever forget to set debug="false" before deploying.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Posted by Jeff on Monday, May 05, 2008 1:38 PM
Permalink | Comments (1) | Post RSSRSS comment feed

Comments

Andre de

Wednesday, May 14, 2008 8:52 AM

Andre

And there is so much more:
- don´t use viewstate, whenever not necessary
- remove viewstate, when not needed (form runat="server" causes a viewstate wether it´s deactivated or not)
- use caching
- use connection pooling
- use content delivery network
etc Smile

Add comment


(Will show your Gravatar icon)  

  Country flag

[b][/b] - [i][/i] - [u][/u]- [quote][/quote]



Live preview

Thursday, November 20, 2008 7:51 AM