5 ms·

Apache 2.4 with event MPM should give you comparable performance to nginx

TylerE 13y ago
Looks more like a factor of 2 difference to me: http://blog.zhuzhaoyuan.com/2012/02/apache-24-faster-than-nginx/ http://blog.zhuzhaoyuan.com/2012/02/apache-24-faster-than-ng...
- delian66 13y ago
  The article's actual title is "Apache 2.4 Faster Than Nginx?" . As most articles having a question mark at the end of their title, not surprisingly the answer is "no" ... Quoting from the article itself: >> It turned out that it’s a false claim. Apache 2.4 is actually much slower than Nginx!
  - TylerE 13y ago
    Yes, that's what I said. It's a factor of two slower than nginx
DigitalSea 13y ago
Performance is pretty good in Apache 2.4, but compare RAM usage alongside NGINX and you'll notice that 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. Apache is getting better, but it's not really on par with NGINX (yet, but it will be).
- gnaritas 13y ago
  You didn't hear what he said, he's specifically not talking about the memory hogging process bases mpm. You seem to think Apache only works that way, but the worker modules are pluggable.
  - 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 ago
      He'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.

Looks more like a factor of 2 difference to me: http://blog.zhuzhaoyuan.com/2012/02/apache-24-faster-than-nginx/ http://blog.zhuzhaoyuan.com/2012/02/apache-24-faster-than-ng...

delian66 13y ago
The article's actual title is "Apache 2.4 Faster Than Nginx?" . As most articles having a question mark at the end of their title, not surprisingly the answer is "no" ... Quoting from the article itself: >> It turned out that it’s a false claim. Apache 2.4 is actually much slower than Nginx!
- TylerE 13y ago
  Yes, that's what I said. It's a factor of two slower than nginx

DigitalSea 13y ago

Performance is pretty good in Apache 2.4, but compare RAM usage alongside NGINX and you'll notice that 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. Apache is getting better, but it's not really on par with NGINX (yet, but it will be).

gnaritas 13y ago
You didn't hear what he said, he's specifically not talking about the memory hogging process bases mpm. You seem to think Apache only works that way, but the worker modules are pluggable.
- 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 ago
    He'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.