Registry Path:
HKEY_LOCAL_MACHINE\SYSTEM
\CurrentControlSet
\Services
\InetInfo
\Parameters
| CacheSecurityDescriptor REG_DWORD |
| Range: 0, 1 Default: 1 (enabled) |
| Specifies whether security descriptors are cached for file objects. If enabled (with the value of 1), IIS retrieves security permissions when caching a file object and will not need to gain access to the file object to check access rights for new users. The feature is useful only if you have more than one user account (not using anonymous only). By default, IIS does not cache security descriptors, but checks the access rights against the file object for new user accounts. |
| CheckCertRevocation REG_DWORD |
| Range: 0, 1 Default: 0 (disabled) |
| Specifies whether client certificates are checked for revocation by IIS. By default this is disabled because checking is typically done over the Internet for common certificate issuers and has severe performance impact. Enabling checking may be useful if you issue your own certificates and the revocation process is local. |
| DisableMemoryCache REG_DWORD |
| Range: 0, 1 Default: 0 (disabled) |
| Disables server caching. This key cannot be configured by using Internet Service Manager. |
| ListenBackLog REG_DWORD |
| Range: 1 - 250 Default: 15 |
| Specifies the maximum number of active connections to hold in the queue waiting for server attention. Enhanced IIS functionality generally makes it unnecessary to use or modify this entry, although extremely heavy use might benefit by increasing this value up to 50. |
| MaxConcurrency REG_DWORD |
| Range: 0 - unlimited Default: 0 |
| Specifies the amount of concurrency that a system should provide. Completion ports are used by IIS for handling input-output (I/O). In general it is not good to have more than one thread running and conflicting on shared memory or locks. This key specifies how many threads per processor should be allowed to run simultaneously if there is a pending I/O operation. The specific value of 0 allows the system to make the intelligent choice of the number of threads to use. Any nonzero value specifies that the system should allow that many threads per processor to run simultaneously. |
| MaxPoolThreads REG_DWORD |
| Range: 0 - unlimited Default:4 |
| Specifies the number of pool threads to create per processor. Each pool thread watches for the network request and processes it. The MaxPoolThreads count does not include threads that are consumed by ISAPI applications. By default, only four CGI applets can run concurrently. If you run many CGI applications, you should increase this value in order to increase the throughput. Optionally, you could set the UsePoolThreadForCGI value (under ..\Services\W3SVC\Parameters) to FALSE (0), but this is somewhat dangerous because it can significantly decrease performance during high usage of CGI applications. Generally, it is not good to create more than 20 threads per processor. |
| PoolThreadLimit REG_DWORD |
| Range: 0 - unlimited Default: 2 * # MB |
| Specifies the maximum number of pool threads that can be created in the system. Each pool thread watches for the network request and processes it. PoolThreadLimit is a hard limit that includes all IIS threads. PoolThreadLimit will always be greater than or equal to MaxPoolThreads. |
| MinFileKbSec REG_DWORD |
| Range: 1 - 8192 Default: 1000 |
| When a Web server sends a file to a client, a timeout is established for how long the server will allow the transfer to continue before ending it. The timeout chosen is the maximum of the Connection Timeout specified in Internet Service Manager plus the size of the file divided by the value specified as MinFileKbSecs. For example, a file size of 100 kilobytes is given a timeout of 100 seconds, or the Connection Timeout if the latter is greater. Note that the registry name is misleading, because the value is in bytes, not kilobytes as the name implies. |
| ObjectCacheTTL REG_DWORD |
| Range: 0 - unlimited Default: 30 seconds |
| This registry entry controls the Time To Live (TTL) setting, which defines the length of time that objects are held in cached memory. If an object in the memory cache has not been referenced for the defined period, that object will be phased out of the cache. If system memory is limited or the server's contents are dynamic, you can use a lower TTL to prevent system memory from being used to cache a large number of volatile objects. Setting the value to 0xFFFFFFFF disables the object-cache scavenger and allows cached objects to remain in the cache until they are overwritten. Disabling the cache scavenger is useful if your server has ample system memory and your data is relatively static. |
| ThreadTimeout REG_DWORD |
| Range: 0 - unlimited Default: 24*60*60 (24 hours) |
| Specifies the amount of time an input-output processing thread should be maintained even if there is no I/O activity on the system. In general when there is no I/O activity and no requests outstanding the server is idle and does not consume memory. But if that situation prolongs and exceeds the ThreadTimeout interval, then the thread is stopped. Units are in seconds. |
| UserTokenTTL REG_DWORD |
| Range: 0 - 0x7FFFFFFF Default: 15 * 60 (10 Minutes) |
| When a request is made to the server, the security credentials for the request (or the configured anonymous user) are used to create a user token on the server which the server impersonates when accessing files or other system resources (see CacheSecurityDescriptor). The token is cached so that the Windows NT logon takes place only the first time the user accesses the system or after the user's token has fallen out of the cache. Windows NT Challenge/Response authentication tokens are not cached. Units are in seconds. |