<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Analyzing Common CLR Performance Problems</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx</link><description>How To Use This document This document is intended to help you diagnose common CLR performance issues. Over the years we have seen a wide variety of CLR performance issues from our customers. This document tries to classify these issues in broad categories</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Analyzing Common CLR Performance Problems</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#153876</link><pubDate>Sat, 12 Jun 2004 00:26:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:153876</guid><dc:creator>Pavel Lebedinsky</dc:creator><description>&amp;gt; Observe &amp;quot;Process\Private Bytes&amp;quot; perf counter&lt;br&gt;&amp;gt; or &amp;quot;MemUsage&amp;quot; column in the task manager&lt;br&gt;&lt;br&gt;&amp;gt; Observe &amp;quot;Process\Virtual Bytes&amp;quot; perf counter&lt;br&gt;&amp;gt; or &amp;quot;Virtual Memory Size&amp;quot; column in the task&lt;br&gt;&amp;gt; manager.&lt;br&gt;&lt;br&gt;This is a common source of confusion. MemUsage in task manager is actually Process\Working Set, and VMSize is Process\Private Bytes.&lt;br&gt;&lt;br&gt;Task manager doesn't have a counter that corresponds to Process\Virtual Bytes.&lt;br&gt;&lt;br&gt;&amp;gt; You can also use !inetdbg.vmmap command in&lt;br&gt;&amp;gt; ntsd/windbg.&lt;br&gt;&lt;br&gt;Inetdbg.dll doesn't seem to be included with debuggers (&lt;a target="_new" href="http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx"&gt;http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx&lt;/a&gt;). I usually use !address to get vadump-like output from cdb. It also prints a nice memory usage summary at the end.&lt;br&gt;&lt;br&gt;&amp;gt; E.g. !heap 0 would show calls to HeapAlloc&lt;br&gt;&amp;gt; with no corresponding calls to HeapFree&lt;br&gt;&lt;br&gt;!heap 0 just displays basic info about all heaps in the process. Latest debuggers do have several commands that are very useful for troubleshooting unmanaged heap leaks (!heap -stat, !heap -l).</description></item><item><title>re: Analyzing Common CLR Performance Problems</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#154469</link><pubDate>Sun, 13 Jun 2004 07:09:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:154469</guid><dc:creator>Saurabh Nandu</dc:creator><description>Great Post! </description></item><item><title>Generic Managed code Debugging plus understanding the whys/hows pointers</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#173185</link><pubDate>Mon, 05 Jul 2004 15:16:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:173185</guid><dc:creator>govind on web</dc:creator><description /></item><item><title>Good GC reading</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#235504</link><pubDate>Wed, 29 Sep 2004 03:16:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:235504</guid><dc:creator>markorangel.com</dc:creator><description /></item><item><title>Tools that help diagnose managed memory related issues</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#254291</link><pubDate>Tue, 09 Nov 2004 10:03:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:254291</guid><dc:creator>Maoni's WebLog</dc:creator><description /></item><item><title>Tools that help diagnose managed memory related issues</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#254305</link><pubDate>Tue, 09 Nov 2004 10:12:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:254305</guid><dc:creator>Maoni's WebLog</dc:creator><description /></item><item><title>Tools that help diagnose managed memory related issues</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#254308</link><pubDate>Tue, 09 Nov 2004 10:13:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:254308</guid><dc:creator>Maoni's WebLog</dc:creator><description /></item><item><title>Debugging - CLR performance problems</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#256382</link><pubDate>Fri, 12 Nov 2004 14:42:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:256382</guid><dc:creator>ThoughtChain</dc:creator><description /></item><item><title>re: Tracking down managed memory leaks </title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#331255</link><pubDate>Thu, 23 Dec 2004 18:11:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:331255</guid><dc:creator>Jackie Goldstein's Weblog</dc:creator><description /></item><item><title>Tools that help diagnose managed memory related issues</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#1041889</link><pubDate>Thu, 09 Nov 2006 04:08:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1041889</guid><dc:creator>Maoni's WebLog</dc:creator><description>&lt;p&gt;I was writing an internal wiki page on performance and thought this info is useful to many external readers&lt;/p&gt;
</description></item><item><title>Committed Memory issue | keyongtech</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#9363186</link><pubDate>Thu, 22 Jan 2009 08:25:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9363186</guid><dc:creator>Committed Memory issue | keyongtech</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.keyongtech.com/508940-committed-memory-issue"&gt;http://www.keyongtech.com/508940-committed-memory-issue&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>[VB.NET][CF] lib?ration de m?moire sur Pocket PC | hilpers</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#9368193</link><pubDate>Thu, 22 Jan 2009 18:06:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9368193</guid><dc:creator>[VB.NET][CF] lib?ration de m?moire sur Pocket PC | hilpers</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.hilpers.fr/962920-vb-net-cf-liberation-de"&gt;http://www.hilpers.fr/962920-vb-net-cf-liberation-de&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Akhune s WebLog Analyzing Common CLR Performance Problems | alternative dating</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#9767973</link><pubDate>Wed, 17 Jun 2009 10:32:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9767973</guid><dc:creator> Akhune s WebLog Analyzing Common CLR Performance Problems | alternative dating</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://topalternativedating.info/story.php?id=11873"&gt;http://topalternativedating.info/story.php?id=11873&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Akhune s WebLog Analyzing Common CLR Performance Problems | home lighting</title><link>http://blogs.msdn.com/akhune/archive/2004/06/11/153734.aspx#9779893</link><pubDate>Fri, 19 Jun 2009 08:49:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9779893</guid><dc:creator> Akhune s WebLog Analyzing Common CLR Performance Problems | home lighting</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://homelightingconcept.info/story.php?id=2028"&gt;http://homelightingconcept.info/story.php?id=2028&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>