Powered by Blogger.

Saturday, March 1, 2014

Performance Monitoring in ASP.Net 4.0



In this post we will discuss about Performance Monitoring in ASP.Net 4.0.

Also you can check out:

- How To Call a Button Click From Another Button in C#.Net?

- Triggers in sql server 2008

- Convert first letter to uppercase in C#.Net

In order to increase the number of Web sites that can be hosted on a single server, many hosters run multiple ASP.NET applications in a single worker process. However, if multiple applications use a single shared worker process, it is difficult for server administrators to identify an individual application that is experiencing problems.

ASP.NET 4.0 provides new resource-monitoring functionality introduced by the CLR. To enable this functionality,  add the following XML configuration snippet to the aspnet.config configuration file.

<?xml version="1.0" encoding="UTF-8" ?>
<configuration>
  <runtime>
    <appDomainResourceMonitoring enabled="true"/>
  </runtime>
</configuration>
   
 The aspnet.config file is in the directory where the .NET Framework is installed. It is not the Web.config file.

When the appDomainResourceMonitoring feature has been enabled, two new performance counters are available in the "ASP.NET Applications" performance category: % Managed Processor Time and Managed Memory Used. Both of these performance counters use the new CLR application-domain resource management feature to track estimated CPU time and managed memory utilization of individual ASP.NET applications. As a result, with ASP.NET 4, administrators now have a more granular view into the resource consumption of individual applications running in a single worker process.





0 comments

Post a Comment