<?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>ASP.NET and Performance</title><link>http://blogs.msdn.com/tom/archive/2008/06/23/asp-net-and-performance.aspx</link><description>I wanted to talk about monitoring performance in ASP.NET for a bit.&amp;#160; I have already posted a few postings that talk around this issue, namely: ASP.NET Debugging - High Memory part 5 – Fragmentation ASP.NET Debugging - ASP.NET Tips- How to use DebugDiag</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>ASP.NET and Performance</title><link>http://blogs.msdn.com/tom/archive/2008/06/23/asp-net-and-performance.aspx#8643253</link><pubDate>Mon, 23 Jun 2008 21:30:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8643253</guid><dc:creator>DotNetKicks.com</dc:creator><description>&lt;p&gt;You've been kicked (a good thing) - Trackback from DotNetKicks.com&lt;/p&gt;
</description></item><item><title>ASP.NET Tips: Finding what is taking up memory</title><link>http://blogs.msdn.com/tom/archive/2008/06/23/asp-net-and-performance.aspx#8653003</link><pubDate>Wed, 25 Jun 2008 22:46:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8653003</guid><dc:creator>ASP.NET Debugging</dc:creator><description>&lt;p&gt;There are some times that you want to figure out what is taking up your memory.&amp;amp;#160; There are a few&lt;/p&gt;
</description></item></channel></rss>