Live data from Hacker News

The Raspberry Pi web server speed test

jeremymorgan.com

11–19 of 19 posts

Re: The Raspberry Pi web server speed test

#11

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 charts show nginx has lower availability at 200 concurrent connections except for the large JPG test where availability is the same (97.55%). The labels are goofed up on the second chart (they're off by a column), so maybe that's what confused you.

Re: The Raspberry Pi web server speed test

#12
I feel like the load is way too high for getting relevant results. Imho it doesn't really matter if response time is 15 or 35 seconds when most users except responses in Also it would have been nice to see some low-power x86 system for comparison.

Re: The Raspberry Pi web server speed test

#15

I 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.

+1 for this. Go can hammer out requests spectacularly. We're using it to shift out static content (all from RAM).

Re: The Raspberry Pi web server speed test

#16

I 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.

I don't think either of those would perform as well as just a stripped down epoll shim, which is basically just stripped down nginx.

Re: The Raspberry Pi web server speed test

#17
post #4

FYI 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.

Maybe Apache should have a braindead on/off setting, so it works better than Nginx after a single tweak.

Re: The Raspberry Pi web server speed test

#18
Could anybody explain why there is such a difference between text and image? Is this just because the file sizes are different or has that a different cause?

I 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.

Post reply on HN