Article ID: 815156 - Last Review: May 12, 2007 - Revision: 4.4 How to restrict ASP.NET to specific processors in a multiprocessor systemOn This PageSUMMARYThis step-by-step article describes how you can restrict
ASP.NET to use specific processors in a multiprocessor system. You can
configure ASP.NET applications to use specified processors in a multiprocessor
system. This is useful to control the overall performance effect that Web
applications may have on a server. When you restrict multiple ASP.NET
applications to certain processors on a single server, you limit the
opportunity for an application to affect the performance of another
application. This is particularly useful when the ASP.NET application executes
on the same physical server as the SQL Server, and the SQL Server configuration
specifies different processors. Note In most cases, you can reach optimal performance if you allow all processes to use all processors. Processor usage for ASP.NET must be restricted only to limit the effect on other processes. Configure the processModel elementTo force an ASP.NET application to use specific processors, you must convert a binary number to determine the correct settings. Then you can edit the Web.config file for the application. In the Web.config file, you add or you modify the processModel element. To do this, follow these steps:
REFERENCES For additional information, click the following article
number to view the article in the Microsoft Knowledge Base: 818015
(http://support.microsoft.com/kb/818015/
)
How to tune and scale performance of applications that are built on the .NET Framework
For more information about the <processModel> element, visit the following Microsoft Web site: http://msdn2.microsoft.com/en-us/library/7w2sway1(vs.71).aspx
(http://msdn2.microsoft.com/en-us/library/7w2sway1(vs.71).aspx)
For more information about the <section> element, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/aa309408(VS.71).aspx
(http://msdn2.microsoft.com/en-us/library/aa309408(VS.71).aspx)
| Article Translations
|
Back to the top
