Why My ASP.NET Application's Performance Is Less Than Optimal?

From my recent engagements I collected few performance anti-patterns that make ASP.NET web application to perform the way that is less than optimal. Many related to architecture and design. Below is the list of the anti-patterns and related materials on how to identify, analyze, and fix it. Have fun - if you feel like sharing your own experiences - that would rock my world!

by striatic

Why My ASP.NET Application Slow?

• Improper HTML Rendering
  • ASP.NET Performance Sin - Serving Images Dynamically (Or Another Reason To Love Fiddler)
  • Improve Web Application Performance By Reducing Number Of Http Requests - Fiddler To The Rescue
• Large data volumes sent over the wire
  • Identify ASP.NET, Web Services, And WCF Performance Issues By Examining IIS Logs
• Complex algorithms, casting, serialization costs
  • Best ASP.NET Performance Winner For Data Binding - Hands Up To Response.Write()
• Chatty database access
  • Performance Sin - Chatty Database Access And Loops (Plus Another Free Performance Tool)
• Session overuse – blows your RAM causing working process recycles
  • Identifying Memory Leak With Process Explorer And Windbg
• Long running operations – locking on worker threads (threadpool)
• Synchronous communications w/downstream resources (web services, databases)
  • Improve ASP.NET 2.0 Performance With PageAsyncTask - Multithreading For The Masses
• Locking files (notice the low CPU in the picture below - this is where the application is locked with teh following excetion)
  • Exception message: The process cannot access the file 'c:\inetpub\wwwroot\webapp\my.log' because it is being used by another process.

• Serialization
  • Best ASP.NET Performance Winner For Data Binding - Hands Up To Response.Write()
• Dynamic compilation
  • ASP.NET Performance: Dynamically Loaded Assemblies Cause Application Recycles (Problem and Solution)
• ViewState
  • How To Keep ASP.NET ViewState On The Server – Revised
  • Improve ASP.NET Performance By Disabling ViewState And Setting Session As ReadOnly
• Chatty resources access
  • Performance Sin - Chatty Database Access And Loops (Plus Another Free Performance Tool)

This post is made with PracticeThis.com plugin for Windows Live Writer

Comments

• Anonymous
  March 06, 2009
  Great list!!Linked to the session overuse I would add "beware of session overuse when moving it to out-of-proc (ie. sql state server)" one more latency point is introduced (network, db access)
• Anonymous
  March 06, 2009
  Thank you, Jaime!Your point regarding the out-of-proc session is generally very good. The thing is that I compiled the list based on my own experiences - something i personally dealt with. I never hit out-of-proc session DB or Service.Anyway, thanks for the insight!
• Anonymous
  March 08, 2009
  .NET ASP.NET Routing performance compare to HttpHandler LINQ on Objects Performance Why My ASP.NET Application
• Anonymous
  March 08, 2009
  .NETASP.NETRoutingperformancecomparetoHttpHandlerLINQonObjectsPerformanceWhy...
• Anonymous
  March 08, 2009
  You are voted (great) - Trackback from Web Development Community