Article ID: 810259 - View products that this article applies to.
You cannot configure the minimum number of Worker threads or I/O threads in the ThreadPool class.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 08-Nov-2002 17:34 1.0.3705.374 196,608 Aspnet_isapi.dll 08-Nov-2002 17:26 4,169 Aspnet_perf.h 08-Nov-2002 17:26 20,468 Aspnet_perf.ini 08-Nov-2002 17:26 20,342 Aspnet_perf2.ini 08-Nov-2002 17:34 1.0.3705.374 24,576 Aspnet_regiis.exe 08-Nov-2002 17:34 1.0.3705.374 28,672 Aspnet_wp.exe 08-Nov-2002 16:52 1.0.3705.374 69,632 Corperfmonext.dll 10-Nov-2002 14:56 1.0.3705.374 1,953,792 Mscorlib.dll 31-Oct-2002 18:04 10,252 Mscorlib.ldo 08-Nov-2002 16:51 1.0.3705.374 2,269,184 Mscorsvr.dll 08-Nov-2002 16:51 1.0.3705.374 2,269,184 Mscorwks.dll 22-Aug-2002 19:23 15 Smartnav.htm 22-Oct-2002 13:41 8,728 Smartnav.js 20-Mar-2002 13:31 7,003 Smartnavie5.js 10-Nov-2002 14:59 1.0.3705.374 1,187,840 System.web.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Functionality has been added to the common language runtime ThreadPool class that permits you to configure the minimum number of Worker threads and I/O threads during load.
Microsoft recommends that you tune the minimum number of threads only when there is load on the Web server for only short periods (0 to 10 minutes). In these cases, the ThreadPool does not have enough time to reach the optimal level of threads to handle the load.
If the minimum number of Worker threads or I/O threads is configured, the ThreadPool immediately creates new threads up to the minimum number specified (the default is 0) during a time of high load. After inactivity, these threads die.
The following two APIs have been added to the ThreadPool class:
ThreadPool ClassTwo new configuration settings have been added to the <processModel> configuration section in the Machine.config to use the new ThreadPool class functionality from ASP.NET:
Article ID: 810259 - Last Review: May 23, 2007 - Revision: 3.9