Servers in the WIN7 IIS7 default configuration can handle up to 5,000 requests at the same time, which can cause server errors if the simultaneous request exceeds 5000 due to certain conditions (program issues, etc.). To do this, modify the server's settings to support 100,000 simultaneous requests.
The settings are as follows:
1. Adjust the IIS7 application pool Queue length
Open, click IIS Manager > Application Pools > Advanced settings, and modify the queue length to 65535.
2. Adjust the Appconcurrentrequestlimit settings for IIS 7
Open%systemroot%\system32\inetsrv\config\applicationhost.config, will Appconcurrentrequestlimit The value is changed from default to 100000.
<appconcurrentrequestlimit= "100000"/>
3. Adjust the settings of the Processmodel>requestqueuelimit in Machine.config
Open%windir%\microsoft.net\framework\v4.0.30319\config\machine.config, set the value of requestQueueLimit by default Switch to 100000.
< Configuration > < system . Web > < requestqueuelimit= "100000"/>
4. Modify the registry to adjust the number of simultaneous TCPIP connections supported by IIS 7
In the Hkey_local_machine\system\currentcontrolset\services\http\parameters section, change the default number of connections to 5000 to 100000.
In addition, for large concurrent processing of databases, see the following information:
Http://msdn.microsoft.com/zh-cn/library/aa0416cz.aspx
http://blog.csdn.net/fhzh520/article/details/7757830
http://blog.csdn.net/truong/article/details/8929438
Http://www.cnblogs.com/chuncn/archive/2009/04/21/1440233.html
http://www.baidu.com/s?wd=%E6%95%B0%E6%8D%AE%E5%BA%93%20%E5%A4%A7%E5%B9%B6%E5%8F%91&pn=0&oq=%E6%95%B0% E6%8d%ae%e5%ba%93%20%e5%a4%a7%e5%b9%b6%e5%8f%91&tn=monline_4_dg&ie=utf-8&f=8&rsv_bp=1
Modify Windows Server 2008+iis 7+asp. NET default connection limit, support for massive number of concurrent connections