Increase ThreadsPerChild to support more connections in HttpServer1.log

Hi @Dilshani ,

You can use the following recommendation when setting a value to this parameter. 

ThreadsPerChild: 

Constant number of worker threads in the server process.

 The ThreadsPerChild directive is important. It tells the server how many threads it should use. This is the maximum number of connections the server can handle at once, so be sure to set this number high enough for your system if you expect a lot of concurrent hits.

The default value is ThreadsPerChild 600, but this must be adjusted to reflect the greatest anticipated number of simultaneous connections to accept.

Please note that this is not the same thing as the maximum number of concurrent users. Rather, it sets the maximum number of concurrently executed requests.

With WinNt MPM which is used by IFS, ThreadsPerChild cannot exceed 15 000. However, the real limits are the sum of the fixed startup cost of memory for each thread + the maximum runtime memory usage per thread, which varies based on configuration and workload.

NOTE: A rule of thumb to calculate an appropriate value is to multiply the maximum number of concurrently logged on users by 1.5. This means that the default value will cater for 400 concurrently logged on users doing 200 simultaneous requests.

Hope this helps!

Thanks,

Kasun