StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The managed stack can be profiled in the VS profiler. See:</p> <ul> <li><a href="http://msdn.microsoft.com/en-us/magazine/cc337887.aspx" rel="nofollow">Find Application Bottlenecks with Visual Studio Profiler</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/2s0xxa1d.aspx" rel="nofollow">How to: Profile a Web Site or Web Application Using the Performance Wizard</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/z9z62c29.aspx" rel="nofollow">Analyzing Application Performance by Using Profiling Tools</a></li> </ul> <p>For low level stuff use Xperf, see <a href="http://blogs.technet.com/b/askperf/archive/2008/06/27/an-intro-to-xperf.aspx" rel="nofollow">Two Minute Drill: Introduction to XPerf</a></p> <p>For the SQL Server side there are many methodologies for performance troubleshooting, like <a href="http://technet.microsoft.com/en-us/library/cc966413.aspx" rel="nofollow">Waits and Queues</a>. For specific statement duration/IO cost you can use profiler trace, see <a href="http://msdn.microsoft.com/en-us/library/ms190793%28v=sql.105%29.aspx" rel="nofollow">Scenarios for Using SQL Server Profiler</a>.</p> <p>Now for a very <em>specific</em> and <em>invasive</em> way in your case you can use Performance Counters. Not the stock kind, but create your own. See <a href="http://rusanu.com/2009/04/11/using-xslt-to-generate-performance-counters-code/" rel="nofollow">Using XSLT to generate Performance Counters</a> for an ease way to geenrate the plumbing needed to augment your app with its own perf counters, then hook up your code with performance tracing. Use the standard perofrmance counters tool chain (<a href="http://technet.microsoft.com/en-us/library/bb490956.aspx" rel="nofollow">logman.exe</a>, <a href="http://technet.microsoft.com/en-us/library/bb490957.aspx" rel="nofollow">perfmon.exe</a>) to capture and analyze.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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