Re:New version of Apache HTTP Server released
by lrobb on Tuesday February 21, 2012 @10:21PM
(#3619281)
You've got think about all of the specifics though...
Here's apache tuned to serve static files of 50kb in length, with 20 requests per client, 500 uniques per hour...
vs.
Here's apache tuned to serve a wordpress blog that gets 500 uniques per hour and each client makes 50 requests (average time on site is 5 minutes)...
and then...
apache serving wordpress on a VPS vs apache serving wordpress on a single core vs apache serving wordpress on a quad-core..
and oh-wait... if we're talking php then let's consider prefork/FastCGI/yada yada yada
The "problem" (or as I prefer to look at it: feature) with Apache, is that it's been around for so long, that it can accommodate all of the above specific issues.
Here's apache tuned to serve static files of 50kb in length, with 20 requests per client, 500 uniques per hour...
vs.
Here's apache tuned to serve a wordpress blog that gets 500 uniques per hour and each client makes 50 requests (average time on site is 5 minutes)...
and then...
apache serving wordpress on a VPS vs apache serving wordpress on a single core vs apache serving wordpress on a quad-core..
and oh-wait... if we're talking php then let's consider prefork/FastCGI/yada yada yada
The "problem" (or as I prefer to look at it: feature) with Apache, is that it's been around for so long, that it can accommodate all of the above specific issues.