We have IIS 7 running a classic ASP app. We noticed that while the CPU stays low, the ASP Request Queue can sometimes get high, causing slow response times. After some research it seems changing the max threads per processor setting may be in order.
Until now it was at the default of 25, and we have 6 cores, so 150 threads max. Before changing anything, I noticed that w3wp.exe is always using 150 threads, which seems to suggest more threads may indeed help us.
So we tried changing the value from 25 to 50, and stopped and restarted the server instance, but when looking at the thread count, it still sits at 150.
I would be very surprised if we now have a 300 thread max (50*6 cores) but we happen to just be using 150, the old max. It seems much more likely that the old max is still in place.
Any ideas as to how to make sure the setting is really in effect?
Answer
Attribution
Source : Link , Question Author : Shalom Slavin , Answer Author : Community
