Why shouldn't you always use Apache's event MPM instead of the worker MPM? -


mpm_event mpm_worker except mpm_event manages (non-ssl) keepalive connections separate, dedicated thread rather having each thread manage each individual connection. giving , keeping dedicated thread each keepalive connection, mpm_worker leaves thread , resources bound connection regardless of whether or not request being processed. mpm_event on other hand, can lower system resource use in high concurrency environments allowing thread , resources recycled system once requests complete.

it seems me in high concurrency, non-ssl environments keepalive has long timeouts, mpm_event has potential make system can handle higher workload equivalent resources system same resorces using mpm_worker. more importantly, seems me in terms of resource use , features, mpm_event @ least mpm_worker, if not better, in circumstances.

despite understanding mpm_event @ least , possibly better, favorite linux distributions default using mpm_worker when installing apache 2.4 repositories. makes me wonder if thinking incomplete , if there technical reason missing use mpm_worker rather mpm_event in apache 2.4.

my question therefore correct in saying mpm_worker @ least mpm_event, if not better, in circumstances, , (2) if not, technical benefits there using mpm_worker in apache 2.4?


Comments

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -