4 ms·
Here are the relevant Apache configuration directives for this sort of benchmark of the event or worker MPM. ServerLimit: In combination with ThreadLimit, this
by sciurus 15y ago
Here are the relevant Apache configuration directives for this sort of benchmark of the event or worker MPM.
ServerLimit: In combination with ThreadLimit, this sets the maximum configured value for MaxRequestWorkers. Default is 16.
ThreadLimit: The maximum configured value for ThreadsPerChild for the lifetime of the Apache httpd process. Any attempts to change this directive during a restart will be ignored, but ThreadsPerChild can be modified during a restart up to the value of this directive. Default is 64.
ThreadsPerChild: The number of threads created by each child process. The child creates these threads at startup and never creates more. Default is 25.
MaxRequestWorkers: The limit on the number of simultaneous requests that will be served. Any connection attempts over the MaxRequestWorkers limit will normally be queued, up to a number based on the ListenBacklog directive. Default value is ServerLimit multiplied by the value of ThreadsPerChild, e.g. 400.
ListenBacklog: Maximum length of the queue of pending connections.
Default varies by OS, on linux I think it can't be larger than /proc/sys/net/core/somaxconn
AsyncRequestWorkerFactor: Tunes the event MPM's concurrent connections per process. See http://httpd.apache.org/docs/2.4/mod/event.html http://httpd.apache.org/docs/2.4/mod/event.html Default is 2.