Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The settings that your are talking are part of <a href="http://msdn.microsoft.com/en-us/library/7w2sway1.aspx" rel="nofollow">processModel</a> element under <code>system.web</code> element from machine.config. For IIS6, following are applicable:</p> <blockquote> <pre><code>autoConfig maxIoThreads maxWorkerThreads minIoThreads minWorkerThreads requestQueueLimit responseDeadlockInterval </code></pre> </blockquote> <p>Typically, you will only find <code>autoConfig="true"</code> and not other elements. Auto-config sets the values as per your machine configuration - the tuning is done as per recommended values (see <em>Threading Explained</em> section from <a href="http://msdn.microsoft.com/en-us/library/ms998549" rel="nofollow">this</a> article) which are same as sighted by the link that you have provided.<br> The <a href="http://msdn.microsoft.com/en-us/library/ms998549" rel="nofollow">article</a> although dated, i excellent resource if you want to tune up these settings manually.</p> <p>On the other hand, at the load that you are serving, I would recommend two things (if you haven't tried already)</p> <ul> <li>Use output caching aggressively - even if the data is dynamic, caching for say 30-60 seconds can give a definite boost at your load</li> <li>If you suspect certain requests are hogging too many threads then attempt to move those resources under different app-pool (you can use different web-site with different sub-domain or you can use different virtual directory/application and choose different app-pool)</li> </ul>
 

Querying!

 
Guidance

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