Clarity, Technology, and Solving Problems | PracticeThis.com
WP7 App with Key Windows Azure resources – Slides, Videos, How-To’s, and T-shooting – for quick consumption on the go.
LinkedIn
Following is a list of performance counters I am usually taking to spot low hanging fruits when measuring ASP.NET performance:
\.Processor\%Processor Time \.NET CLR Memory(*)\Allocated Bytes/sec \.NET CLR Memory(*)\% Time in GC \.NET CLR Exceptions(*)\# of Exceps Thrown / sec \.NET CLR Loading(*)\Current Assemblies
\.NET CLR LocksAndThreads(*)\Contention Rate / sec \.NET CLR LocksAndThreads(*)\Current Queue Length \ASP.NET\Requests Queued \ASP.NET\Request Wait Time \ASP.NET\Requests Current \ASP.NET Applications\Requests In Application Queue \ASP.NET Applications\Pipeline Instance Count \ASP.NET Applications\Requests Executing \ASP.NET Applications\Requests/Sec \Web Service\Current ISAPI Extension Requests
\ASP.NET\Request Execution Time
Detailed explanation about each counter and its significance can be found here: Chapter 15 — Measuring .NET Application Performance
I particularly love the following diagram from the guide. The diagram helps brainstorming while identifying root cause of the performance issues identified using the counters: