<?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>[PowerShell Script] Isolating the Threads Consuming High CPU</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx</link><description>When helping my customers with scenarios in which the symptom is high CPU, I very often end up with only a dump file from the application consuming high CPU and nothing else. When you have a high CPU scenario and you have dump files, you need a Performance</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: [PowerShell Script] Isolating the Threads Consuming High CPU</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx#6888956</link><pubDate>Sat, 29 Dec 2007 00:55:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6888956</guid><dc:creator>newsoft</dc:creator><description>&lt;p&gt;Wow, is Reflector.NET officially endorsed by Microsoft anyhow?&lt;/p&gt;
&lt;p&gt;It is a very powerful tool indeed, but I could figure out more &amp;quot;offensive&amp;quot; ways to use it.&lt;/p&gt;</description></item><item><title>re: [PowerShell Script] Isolating the Threads Consuming High CPU</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx#6889773</link><pubDate>Sat, 29 Dec 2007 02:28:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6889773</guid><dc:creator>Roberto Farah</dc:creator><description>&lt;p&gt;Even though the developer that created .NET Reflector works at Microsoft, I don't know if this tool is considered an official tool. Anyway ILDasm, that has similar features, is an official tool:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://msdn2.microsoft.com/en-us/library/d9kh6s92"&gt;http://msdn2.microsoft.com/en-us/library/d9kh6s92&lt;/a&gt;(VS.71).aspx&lt;/p&gt;</description></item><item><title>re: [PowerShell Script] Isolating the Threads Consuming High CPU</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx#8728688</link><pubDate>Sun, 13 Jul 2008 18:25:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8728688</guid><dc:creator>bmassicotte</dc:creator><description>&lt;p&gt;This is great but time consuming with lots of setup. There is an app called IISPeek that does all this for you and will instantly show you what page is being executed, for how long, process id, which app pool, etc... &amp;nbsp;It halped us troubleshoot and fix the offending pages. Just Google it to find it on the net.&lt;/p&gt;
&lt;p&gt;Best of luck&lt;/p&gt;</description></item><item><title>re: [PowerShell Script] Isolating the Threads Consuming High CPU</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx#8729236</link><pubDate>Sun, 13 Jul 2008 21:34:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8729236</guid><dc:creator>Roberto Alexis Farah</dc:creator><description>&lt;p&gt;I've never heard about this tool. I'll check this out, thanks for the information. :)&lt;/p&gt;</description></item><item><title>re: [PowerShell Script] Isolating the Threads Consuming High CPU</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx#9141601</link><pubDate>Tue, 25 Nov 2008 14:36:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9141601</guid><dc:creator>john</dc:creator><description>&lt;p&gt;Roberto, did you have a look as IISPEEK - I can't see a review of it anywhere on the net - so it would be nice to have an independant review of it rather than just a few dubious comments spread around the net&lt;/p&gt;</description></item><item><title>re: [PowerShell Script] Isolating the Threads Consuming High CPU</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx#9142697</link><pubDate>Tue, 25 Nov 2008 22:44:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9142697</guid><dc:creator>Roberto Farah</dc:creator><description>&lt;p&gt;Hi John&lt;/p&gt;
&lt;p&gt;I've never heard about this software before, but I just accessed its website: &lt;a rel="nofollow" target="_new" href="http://iispeek.com/index.php"&gt;http://iispeek.com/index.php&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;It seems to be interesting and useful. The GUI is very beautiful! &lt;/p&gt;
&lt;p&gt;I have to try it...&lt;/p&gt;
</description></item><item><title>[PowerShell Script] PowerDbg v5.0—Using PowerShell to Control WinDbg</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx#9394613</link><pubDate>Wed, 04 Feb 2009 08:05:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9394613</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;I’m very excited to present the new PowerDbg v5.0! There’s just one change, but it’s a HUGE change that&lt;/p&gt;
</description></item><item><title>[PowerShell Script] PowerDbg v5.1—Using PowerShell to Control WinDbg</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx#9490823</link><pubDate>Thu, 19 Mar 2009 21:30:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9490823</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;So, here we go again. This is a minor version with a few new cmdlets. These new cmdlets are those that&lt;/p&gt;
</description></item><item><title>[PowerShell Script] PowerDbg v5.2—Using PowerShell to Control WinDbg</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx#9550097</link><pubDate>Wed, 15 Apr 2009 08:47:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9550097</guid><dc:creator>Debugging Toolbox</dc:creator><description>&lt;p&gt;This version has two improvements and some scripts were changed to be compatible with this new version:&lt;/p&gt;
</description></item><item><title>re: [PowerShell Script] Isolating the Threads Consuming High CPU</title><link>http://blogs.msdn.com/debuggingtoolbox/archive/2007/12/17/powershell-script-isolating-the-threads-consuming-high-cpu.aspx#9871001</link><pubDate>Sat, 15 Aug 2009 15:42:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9871001</guid><dc:creator>eluplecerlova</dc:creator><description>&lt;p&gt;Hello&lt;/p&gt;
&lt;p&gt;I gonna buy new laptop and was thinking what antivirus program to buy?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;</description></item></channel></rss>