<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Real Case: IIS and Asp.Net hanging or poor performance (intermediary)</title><link>http://blogs.technet.com/marcelofartura/archive/2006/10/26/real-case-iis-and-asp-net-hanging-or-poor-performance-intermediary.aspx</link><description>This week I'm working on this case related to IIS6 server hosting an Asp.Net application (it's a C# app) whose the performance is poor even when a very low number of users is hitting it. The architecture is the classical web layer accessing the backend</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>How to Extract SQL info from a thread stack</title><link>http://blogs.technet.com/marcelofartura/archive/2006/10/26/real-case-iis-and-asp-net-hanging-or-poor-performance-intermediary.aspx#1515724</link><pubDate>Fri, 13 Jul 2007 22:49:36 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1515724</guid><dc:creator>Mfartura's blog</dc:creator><description>&lt;p&gt;In the post about troubleshooting Asp.Net poor performance I showed you how to identify one possible&lt;/p&gt;
</description></item><item><title>Worker Threads Never Changes</title><link>http://blogs.technet.com/marcelofartura/archive/2006/10/26/real-case-iis-and-asp-net-hanging-or-poor-performance-intermediary.aspx#3071086</link><pubDate>Sun, 15 Jun 2008 01:21:48 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3071086</guid><dc:creator>jabailo</dc:creator><description>&lt;p&gt;I am optimizing an ASP.NET 2.0 applicaton running on IIS 5.0 on W2K.&lt;/p&gt;
&lt;p&gt;I wrote a c# threaded test application that launches (async) web requests at it. &amp;nbsp; The most I can get through successfully is about 4 or 5 a second.&lt;/p&gt;
&lt;p&gt;Monitoring the ASP2.0 Request Execution Time, it stays stable around 1 second. &amp;nbsp; The application is constrained by a single sproc on SQL server, but I'm managed to get this to run around 1s constantly.&lt;/p&gt;
&lt;p&gt;However, I don't see the processor taxed more than 5%.&lt;/p&gt;
&lt;p&gt;One thing that puzzles me is that the ASP Application Worker Thread counter never goes above 1.&lt;/p&gt;
&lt;p&gt;Based on another articles recommendation, I changed the processModel setting in machine.config to use a max 100 worker threads. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Shouldn't I be seeing more performance from my web server?&lt;/p&gt;</description></item><item><title>PSTools</title><link>http://blogs.technet.com/marcelofartura/archive/2006/10/26/real-case-iis-and-asp-net-hanging-or-poor-performance-intermediary.aspx#3071087</link><pubDate>Sun, 15 Jun 2008 01:31:13 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3071087</guid><dc:creator>jabailo</dc:creator><description>&lt;P&gt;Also, Looking at the VBS script in the article -- have you also tried looking at the thread monitor in the PSTools collection...I've used it in Java. &amp;nbsp; Maybe I should use that instead of perfmon....&lt;/P&gt;</description></item><item><title>re: Real Case: IIS and Asp.Net hanging or poor performance (intermediary)</title><link>http://blogs.technet.com/marcelofartura/archive/2006/10/26/real-case-iis-and-asp-net-hanging-or-poor-performance-intermediary.aspx#3072302</link><pubDate>Tue, 17 Jun 2008 02:33:16 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3072302</guid><dc:creator>Marcelo Fartura</dc:creator><description>&lt;p&gt;I haven't tried used PSTools collection :(&lt;/p&gt;</description></item></channel></rss>