3 ms·
nginx memory footprint is very small, and does an excellent job serving static files. It's widespread usage helps in uncovering security bugs faster too.
by halayli 12y ago
nginx memory footprint is very small, and does an excellent job serving static files. It's widespread usage helps in uncovering security bugs faster too.
- nacs 12y agoI'm not endorsing thttpd/sthttpd over nginx on modern systems and I actually do use nginx pretty much everywhere but thttpd has its uses. Over a decade ago, I have used thttpd to serve static files as: 1) nginx didn't exist 2) thttpd is tiny (thttpd binary size is ~50KB vs nginx's ~2.8MB) which is good on embedded or very old hardware for example. 3) Memory footprint of thttpd is around 10KB. nginx doesn't even come close
- currysausage 12y agoWhat point are you trying to make? That because of the existence of Nginx, every other HTTP server project should be abandoned? Nginx certainly is some kick-ass piece of software, but as every other software, it doesn't suit 100% of users 100%. There are valid reasons to choose different HTTP servers over Nginx, as people in this thread already pointed out. To give another example, the OpenBSD project, famously obsessed about code quality, recently removed Nginx from the base system, not least because they think its code is "über-optimized," possibly eliminating OS-level security mechanisms. [1] This doesn't mean that the code bad, but some people prefer "tiny" and clearly-written codebases that can be audited in reasonable time. thttpd, in particular, seems to hold the balance between code size and performance very well, which makes it a nice choice for embedded systems. [1] <http://undeadly.org/cgi?action=article&sid=20140827065755&pid=24&mode=expanded> http://undeadly.org/cgi?action=article&sid=20140827065755&pi...