Optimising ASP.NET Performance


Something I do a lot with customers is improving their ASP.NET Web Site performance. Most people spend hours looking at server-side performance, but just don’t realise what kind of gains you can get by looking at often-overlooked settings. I’ve seen cases when enabling GZIP compression in IIS and setting up some content expiration headers alone has given over 40% improvement in page load time for the end user (and sometimes up to 70% improvements with a few more tweaks – and that matters over a slow WAN). Those kind of results just can’t be ignored, so if you’re doing any serious web site development make sure you think about it!

I’ve been meaning to blog a list of things to consider when doing this tuning for ages, but just noticed that my exceedingly talented colleagues over the fence in Microsoft Consulting Services UK have just such a list on their team blog… so go check it out;

Common performance issues on ASP.NET web sites

Comments (1)

  1. Shah says:

    performance of an asp.net app can be improved by reducing its trips to database while caching the data. but cache in asp.net is stand alone so it'll do well only in a smaller web farms while in a multi-server environment, the use of a distributed cache can be a better option. some third party products like NCache ( http://www.alachisoft.com/…/asp-net-performance-scalability.html )or Appfabric (http://www.microsoft.com/…/default.aspx)can also help in this regard