Last post Oct 24, 2012 05:30 AM by smirnovvm
Oct 22, 2012 08:31 AM|smirnovvm|LINK
I got strange ASP.NET threadpool behaviour on my test environment (Windows 7 + IIS 7 + .NET 4.0) and can't understand why it behaves so.
The problem is following:
I have test ASP page (Default.aspx) with very simple code inside: Thread.sleep(2000) + log thread ID & Max/Available threads into file. On first call it logs:
If I start concurrent (Apache ab with 200/ 50 concurrent users) stress test for this page I see in log:
Strange thing is that number of available threads in pool NEVER goes less than 790 and of course it impacts my requests per second metric.
To make it use more concurrent threads I tried to setup ASPnet.config and machine.config and it seems what changes applied OK, but my log still shows that only 10 threads used to handle requests. So, my question is : Is there any way to make ASP.NET use
more than 10 threads from threadpool?
Thanks in advance,
Oct 22, 2012 10:09 AM|gerrylowry|LINK
@ smirnovvm welcome to forums.asp.net
sorry, i do not know the answer ...
please note: it appears to me that you are likely to be more successful getting an answer at forums.asp.net's (this forum) sister forum:
Oct 22, 2012 05:45 PM|Paul Linton|LINK
You must backup, modify may cause small furry animals to die, blah, blah, blah. All care no responsibility
(Default of 2 * #MB memory available)
More info at
Oct 24, 2012 05:30 AM|smirnovvm|LINK
Thanks so much, with these settings set I got 16! threads allocated at peak, but still unknown why it doesn't allocate more :( With my settings concurrency can be much more but it doesn't happen.