Allow Windows Server 7+ + IIS to support 100,000 concurrent requests

Transferred from: http://www.cnblogs.com/yxlblogs/p/3330972.html

Because the default configuration was used before, the server can handle up to 5,000 simultaneous requests, and this afternoon, because of a situation that caused simultaneous requests exceeding 5000, the above error occurred.

To avoid such errors, we adjusted the settings according to the relevant documentation to allow the server to support 100,000 concurrent requests from the settings.

The settings are as follows:

1. Adjusting the IIS 7 application pool queue Length

Changed from the original default of 1000 to 65535.

IIS Manager > ApplicationPools > Advanced Settings

Queue length:65535

2. Adjust the Appconcurrentrequestlimit settings for IIS 7

Changed from the original default of 5000 to 100000.

C:\windows\system32\inetsrv\appcmd.exe Set config/section:serverruntime/appconcurrentrequestlimit:100000

You can view this setting in%systemroot%\system32\inetsrv\config\applicationhost.config:

<serverruntime appconcurrentrequestlimit= "100000"/>

3. Adjust the settings of the Processmodel>requestqueuelimit in Machine.config

Changed from the original default of 5000 to 100000.

<configuration>    <system.web>        <processmodel enable= "true" requestqueuelimit= "100000"/>

Reference article: http://technet.microsoft.com/en-us/library/dd425294 (office.13). aspx

4. Modify the registry to adjust the number of simultaneous TCPIP connections supported by IIS 7

Changed from the original default of 5000 to 100000.

REG ADD hklm\system\currentcontrolset\services\http\parameters/v maxconnections/t reg_dword/d 100000

5. Run the command using the settings to take effect

net stop http  & net start  

To complete the above 4 settings, you can support 100,000 concurrent requests, the blog Park blog Server has enabled the above settings.

Allow Windows Server 7+ + IIS to support 100,000 concurrent requests