His testing is very flawed. Look at the availability chart: nginx has higher availability at 200 concurrent connections than at 100? It's simply not possible if the test was the same w/ just a higher concurrent connection count, as he claims. Edit: Yes, it's "possible" that this is something in the nginx code causing it work weird, but I'd say a benchmarker should use some common sense instead of blind reporting, not…
The Raspberry Pi web server speed test
11–19 of 19 posts
Re: The Raspberry Pi web server speed test
#12Re: The Raspberry Pi web server speed test
#13Re: The Raspberry Pi web server speed test
#14Re: The Raspberry Pi web server speed test
#15I would've liked to see a small node.js or Go-based server. When running on an embedded device, you want maximum efficiency, and a full web-server isn't your best bet.
Re: The Raspberry Pi web server speed test
#16I would've liked to see a small node.js or Go-based server. When running on an embedded device, you want maximum efficiency, and a full web-server isn't your best bet.
Re: The Raspberry Pi web server speed test
#17FYI out of the box setting for apache are brain dead. I literally have systems with tweaked setting doing 45k/second hits at less then 10ms latency on Apache. You can't do that with default settings because again the brain dead default settings. I think in general tuning each of these carefully could eek out more performance on any platform especially one with such a small footprint.
Re: The Raspberry Pi web server speed test
#18I really like to "out-of-the-box" comparison, but as others already have stated for apache that doesn't really make sense because apache just doesn't perform well without any configuration changes.