3 ms·
"Here is a benchmark that shows the performance of a watermelon and a large canteloupe lobbed from a trebuchet using different kinds of wood and rope under diff
by peterwwillis 14y ago
"Here is a benchmark that shows the performance of a watermelon and a large canteloupe lobbed from a trebuchet using different kinds of wood and rope under different wind conditions. We tied random weights to each melon for no apparent reason."
What the fuck is the point of a performance benchmark if you didn't tune any settings for performance?
- emn13 14y agoIndeed - this doesn't tell you anything. Was nginx configured well? Was apache? How much difference would it have made? Is the old apache version relevant? Pointless test, unless you intend to use those settings on that software on similar hardware.
- roldenburger 14y agoAgree, you can only compare both, if both are tuned for optimal performance for the specific situation.
- peterwwillis 14y agoHell, it would have been great if they had used a real closed testbed on a local network instead of AWS. That would give you reproducible test results that aren't influenced by things like communal server resources and a communal network. Regardless, they put zero thought into what makes each application work to its peak performance and just picked two random configurations, probably based on defaults that we know to be poor on Apache and advantageous on nginx. Using worker instead of event just adds insult to injury.
- taligent 14y agoCall me stupid. But maybe Apache shouldn't ship defaults that have poor performance ?
- peterwwillis 14y agoWell stupid, Apache ships with the default settings it does for historical expectations of its users. But the application's tuning is driven largely by how you use it, as there are several workers for Apache that all are useful in different situations and require vastly different configuration options. This is to say nothing of the kernel options which also need to be tuned to the application. The defaults are just defaults. They need to be changed to improve performance.
- taligent 14y agoWhat do you mean what is the point ? The obvious assumption with all software is that it is optimised out of the box.
- webjunkie 14y agoOptimized for what? For which circumstances? What software fits all?
- taligent 14y agoOptimized for serving HTTP requests at a high throughput. What possible reason is there for Apache deliberately slowing that down ?
- fpgeek 14y agoAre you serious? Just off the top of my head, how about... - Simplifying the initial setup? - Making the default configuration simpler to understand? - Dialing up logging to make your initial configuration easier to monitor / debug? - Performance options with security implications (e.g. ok if other parts of your infrastructure are up-to-snuff, but otherwise...)? The default configuration should be tuned to the needs of whoever is most likely to be using it. I have a hunch that's far more likely to be people using an Apache server (maybe even a web server) for the first time than people with extreme performance requirements.
- peterwwillis 14y agoIf this wasn't a troll, please rest assured that most software is not optimized out of the box (especially when half the optimizing that affects the application is in the kernel)