3 ms·
if you're going to serve static files, nginx absolutely leaves this in the dust (think 50k rps on a beefy machine)
by rantwasp 6y ago
if you're going to serve static files, nginx absolutely leaves this in the dust (think 50k rps on a beefy machine)
- bdavis__ 6y agoof course it does !!
- kragen 6y agoI would expect so, but did you mean 500k or something? "50k rps on a beefy machine" sounds like about the same as, or maybe even a bit slower than, 20k–30k on this 2011 laptop, which was how fast httpdito was last time I measured it.
- rantwasp 6y agowent back and looked at it. a webserver written in asm for the lols is okay but my point was that you probably want a proven, battle ready web server (along the lines of nginx or apache) if running something in production. So, 50k rps on a vanilla well used/well maintened server > 50k rps on an experiment (and don't get this wrong, it's pretty impressive for what it is)
- kragen 6y agoYeah, I definitely wouldn't advise anyone to run httpdito in production. It's so lacking in observability that it doesn't even log hits, it doesn't do timeouts, and its MIME types are configured by writing in assembly language. But it shows that some surprising things are possible. And it can be handy to serve up some static pages from your laptop to your phone or whatever.
- rantwasp 6y agohttps://gist.github.com/willurd/5720255 https://gist.github.com/willurd/5720255 Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000 http://localhost:8000.
- kragen 6y agoYeah, httpdito is similar to those, but maybe with less security holes and definitely with less dependencies.