Registry key for tuning COM+ thread and activity (303071)

MORE INFORMATION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

In MTS, each package has its own thread pool with a predetermined size limit. However, in COM+, the thread pool is dynamic and has smaller average pool size to avoid excessive thread-switch overhead.

For more information about the differences in threading models between MTS and COM+, click the following article number to view the article in the Microsoft Knowledge Base: However, under certain scenarios, slow middle-tier servers may experience low performance due to the lack of threads and concurrency in COM+ run time. Beginning with Post Microsoft Windows 2000 Service Pack 2 COM+ Rollup Hotfix 10 (which allows COM+ to simulate MTS behavior), the following registry key can be added:

Any value other than zero for the EmulateMTSBehavior value causes the thread pool to emulate MTS behavior, that is, one activity for each thread and 100 maximum threads for each package.

Note With the EmulateMTSBehavior value, as soon as 100 STA threads x 1 activities exist, COM+ starts binding multiple activities to the STA threads. COM+ does this to stay responsive to activation requests.

If you experience performance problems while CPU utilization is low, you can set this value to increase the chance of assigning a thread to your request.

Note The COM+ default settings are optimized and tested for most situations. You should consult Microsoft support professionals before you modify these settings.