From IT Skills
Jump to: navigation, search

Web.config settings for production[edit | edit source]

debug[edit | edit source]

debug="true" is not correct for production environment.

maxConcurrentRequestsPerCPU, maxConcurrentThreadsPerCPU etc[edit | edit source]

thread pool can become depleted under heavy load, and remember by default heavy load is more than just 200 simultaneous requests assuming a dual CPU Server

http://stackoverflow.com/questions/4571118/how-to-increase-thread-pool-threads-on-iis-7-0

maxConcurrentThreadsPerCPU[edit | edit source]

.NET Framework v4.0 (as compared to 3.5 or 2.0) is that the default for maxConcurrentRequestsPerCPU was increased to 5000 from 12

on client side[edit | edit source]

Default is 2

/system.net/connectionManagement/add address="*" maxconnection="100"

// maximum number of concurrent connections allowed by a ServicePoint object

System.Net.ServicePointManager.DefaultConnectionLimit = Int16.MaxValue;

async=”false”[edit | edit source]

Category:Testing and measuring applications and IIS performance testing[edit | edit source]

IIS has limitation for concurrent requests. For example, Windows 8 Pro or Windows 7 Ultimated are restricted to 10 as stated in http://weblogs.asp.net/owscott/windows-8-iis-8-concurrent-requests-limit. Such limits are impossible to increase.

For testing we have to use Server windows.