Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>This article from Microsoft covers <a href="http://msdn.microsoft.com/en-us/library/ff647813%28v=pandp.10%29.aspx" rel="nofollow noreferrer">Tuning .Net Application Performance</a> and highlights which counters to collect and compare to determine CPU and I/O bound applications.</p> <p>You sound like you want to monitor this during execution and bypass your cache when things get intensive. Would this not just move the intensive processing from the cache calls to your database calls? Surely you have the cache to avoid expensive DB calls.</p> <p>Are you trying to repopulate an invalidated cache? What is the affect of serving stale data from the cache? You could just lock on the re-populating function and serve stale data to other requests until the process completes.</p> <p>Based on the above article, we collect the following counter objects during our tests and that gives us all the necessary counters to determine the bottlenecks.</p> <ul> <li>.NET CLR Exceptions</li> <li>.NET CLR Memory</li> <li>ASP.NET Applications</li> <li>ASP.NET</li> <li>Memory</li> <li>Paging File</li> <li>Processor</li> <li>Thread</li> </ul> <p>The sections in the article for <a href="http://msdn.microsoft.com/en-us/library/ff647813(v=pandp.10).aspx#scalenetchapt17_topic13" rel="nofollow noreferrer">CLR Tuning</a> and <a href="http://msdn.microsoft.com/en-us/library/ff647813(v=pandp.10).aspx#scalenetchapt17_topic14" rel="nofollow noreferrer">ASP.NET Tuning</a> highlight the bottlenecks that can occur and suggest configuration changes to improve performance. We certainly made changes to the thread pool settings to get better performance.</p> <p><a href="http://msdn.microsoft.com/en-us/library/s155t6ta%28VS.71%29.aspx" rel="nofollow noreferrer">Changing and Retrieving Performance Counter Values</a> might help with accessing the existing Processor counter via code but this isn't something I've tried personally.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload