4 ms·
He's talking about Apache MPM Worker which while offering better performance over the traditional Apache MPM Prefork because it's threaded based like NGINX is,
by DigitalSea 13y ago
He's talking about Apache MPM Worker which while offering better performance over the traditional Apache MPM Prefork because it's threaded based like NGINX is, it still consumes more RAM than NGINX does, so my point remains...
- nisa 13y agoHe's talking about MPM Event¹. It's different from worker and probably not as light as nginx but for most stuff it should compare well. 1: https://httpd.apache.org/docs/current/mod/event.html https://httpd.apache.org/docs/current/mod/event.html
- gnaritas 13y ago> NGINX's event based threads approach takes a big dump all over Apache's separate process lets consume every bit of available RAM the server has until it starts throwing errors and filling log files. No your point doesn't stand, your point is completely wrong because you don't know what you're talking about. Go back read the crap you wrote before claiming your point still stands.