Re:Taobao's branch of Nginx
by mercurial on Tuesday November 13, 2012 @02:47AM
(#4776935)
Anyone outside of Taobao using this in production? I'd be really interested in a reliable version of nginx supporting dynamic loading of modules, recompiling nginx everytime you need a custom module quickly loses its charm.
Re:Taobao's branch of Nginx
by mercurial on Tuesday November 13, 2012 @06:07AM
(#4777381)
If you compare to another sever like Apache which supports dynamic modules, adding a single line in a configuration file (or at worst dropping a .so in a folder, followed by adding a line in a configuration file) is much less work than retrieving gcc and friends and rebuilding a .deb.
Re:Taobao's branch of Nginx
by beagle3 on Tuesday November 13, 2012 @01:16PM
(#4779540)
Dropping a new nginx binary and live-migrating to it takes as much time as doing the same on Apahce with a new .so
Have you ever actually used nginx? I compile it from source with much-less-than-everything for security reasons (e.g., no proxy, no email, no ssi, no ssl, not any of the other ten modules that come by default), and in the 3 times that I needed a module later, it was a quick ./configure;make;make install;kill -SIG2 (or whatever the signal is to switch to a new version), which was not more painful than I remember from my apache days of 5 years ago.
Re:Taobao's branch of Nginx
by mercurial on Tuesday November 13, 2012 @04:17PM
(#4780658)
I count 67 different modules in /etc/apache2/mods-available. Which means you rarely a new .so. On the other hand, Nginx is much more limited in functionalities out-of-the-box.
How do you handle deployment of your custom nginx on several boxes?
Re:Taobao's branch of Nginx
by beagle3 on Tuesday November 13, 2012 @09:45PM
(#4781776)
The same way I handle deployment of everything else. The binary is just one file (/usr/sbin/nginx). Distributing config and restarting processes is the same as with apache.
(My recent nginx deployment have 2 machines, so I do it manually, but in the past, I had a homegrown solution that would pull files from version control, and if they changed, asked the binary to restart)
Re:Taobao's branch of Nginx
by pestaa on Tuesday November 13, 2012 @04:40AM
(#4777206)
Perhaps dynamic loading is useful to speed up tinkering with development and staging, but for production I'll take a system with the least moving parts any day.
Re:Taobao's branch of Nginx
by beagle3 on Tuesday November 13, 2012 @10:59AM
(#4778621)
nginx compiles quickly enough that a script for "service nginx reload" could recompile and replace the binary, and it will only be a little slower than "service apache reload" will be.
It's like a sausage, you can enjoy eating it without seeing how it's made.
Re:Taobao's branch of Nginx
by beagle3 on Tuesday November 13, 2012 @02:31PM
(#4780085)
I don't think any other popular http server support this. If there's a web server written in Erlang, you can be sure that is available (it's a core Erlang feature).
But apache can let you load a new .so without recompiling (or even restarting) the main server, which, for most intents and purposes, gives you equivalent functionality.
Re:Taobao's branch of Nginx
by sbarre on Tuesday November 13, 2012 @08:56AM
(#4777960)
I think this sub-thread may be missing the point that on a production server you may not have installed the whole toolchain required to re-compile your webserver so dynamic module support is actually kind of a bigger deal than you might think.
Re:Taobao's branch of Nginx
by pyre on Tuesday November 13, 2012 @10:57AM
(#4778614)
Well, the idea solution is that you don't compile things directly on your web server. There's no reason you can't compile it on a workstation and package it for deployment to production. Consider what you would be doing if you had a cluster of web servers. Would you compile manually on each server, or create a package (rpm/deb/tgz/etc) and deploy?
Re:Taobao's branch of Nginx
by mercurial on Tuesday November 13, 2012 @04:21PM
(#4780685)
No. But as I pointed out above, Apache comes with 67 modules out-of-the box on Debian, which means you're much less likely to need a custom package, as opposed to the (relative) hassle with nginx. This is why I very much look forward to seeing nginx with reloadable modules.
Re:Taobao's branch of Nginx
by mercurial on Tuesday November 13, 2012 @04:11PM
(#4780626)
Well, the point is, Apache comes with enough modules that I never had any need to actually go and compile a custom one. And since they can be loaded at runtime, in terms of memory you only pay for what you use.
I haven't used nginx often, but the default Debian nginx doesn't come with many things included, I find.
Re:Taobao's branch of Nginx
by gadders on Tuesday November 13, 2012 @09:51AM
(#4778221)
Slightly off-topic, but are there any other major open-source projects from China? I was wondering whether a) there aren't many (yet) or b) they're mostly publicised in Chinese so off the radar for English speakers.
Re:Taobao's branch of Nginx
by yaoweibin on Tuesday November 13, 2012 @11:29AM
(#4778794)
Have you heard of the LVS? (http://www.linuxvirtualserver.org/). We are using it for load balance before Tengine. It's steady and high performance, even better than the commercial load balancer.
I like the idea of combined javascript and stylesheets but I'd rather force the combining from the server-side, not a special client-side request. ie.
Ohhh... agentzh wrote the fork? The one who made many popular modules?"No, nginx will not support logging to a pipe since this is simlpy waste of CPU."
- Igor Sysoev (http://markmail.org/message/4bsjfjpg2kgsjhph)
I always though piped logging was required to rotate logs without restart.
I love the graceful restart and even the replace the executable on the fly nginx has.
Tengine is maintained by many other developers (in Chinese): https://github.com/taobao/tengine/wiki/%E7%A4%BE%E5%8C%BA%E5...
https://github.com/taobao/nginx-http-concat
and another attempt by someone else here:
https://github.com/lindsayevans/nginx-static-concat
But both of them rely on or accept client-side concat, I'd rather just do it server-side only for security/control.
In our experience it's every bit as reliable as mainline nginx.
Also, you can upgrade nginx binary without any downtime, see: http://wiki.nginx.org/CommandLine
Have you ever actually used nginx? I compile it from source with much-less-than-everything for security reasons (e.g., no proxy, no email, no ssi, no ssl, not any of the other ten modules that come by default), and in the 3 times that I needed a module later, it was a quick ./configure;make;make install;kill -SIG2 (or whatever the signal is to switch to a new version), which was not more painful than I remember from my apache days of 5 years ago.
(Has apache changed since then?)
How do you handle deployment of your custom nginx on several boxes?
(My recent nginx deployment have 2 machines, so I do it manually, but in the past, I had a homegrown solution that would pull files from version control, and if they changed, asked the binary to restart)
[I'm a huge nginx fan myself but recall that this is coming to the main project soonish.]
It's like a sausage, you can enjoy eating it without seeing how it's made.
But apache can let you load a new .so without recompiling (or even restarting) the main server, which, for most intents and purposes, gives you equivalent functionality.
But I bet for developing modules, loading standalone is a huge help.
I haven't used nginx often, but the default Debian nginx doesn't come with many things included, I find.