This is part II of measuring .NET application performance. The .NET Framework provides a series of performance counters, which you can monitor using System Monitor and other monitoring tools. To measure other aspects of .NET application performance, you need to add instrumentation to your applications.
Read the full post

In this article of our ASP.NET performance series, we’ll discuss Deployment Considerations. Physical deployment plays an important role in determining the performance and scalability characteristics of your application. Unless you have a compelling reason to introduce a remote middle tier, you should deploy your Web application’s presentation, business, and data access layers on the Web server. The only remote hop should be the hop to the database.
Read the full post

In this article of our ASP.NET performance series, we’ll address the best practices for Data Access. Almost all ASP.NET applications use some form of data access. Data access is typically a focal point for improving performance because the majority of application requests require data that comes from a database.
Read the full post

In our last article in the ASP.NET series we discussed String Management. In this article we’ll address the best practices for Exception Management. Exceptions are expensive. By knowing the causes of exceptions, and by writing code that avoids exceptions and that handles exceptions efficiently, you can significantly improve the performance and scalability of your application.
Read the full post