71–77 of 77 posts
Does this mean if a crash occurs, the whole process of nginx will crash? Whereas Apache's processes can be restarted?
/Genuinely curious
"Nginx uses an asynchronous event-driven approach to handling requests which provides more predictable performance under load, in contrast to the Apache HTTP server model that uses a threaded or process-oriented approach to handling requests." Does this mean if a crash occurs, the whole process of nginx will crash? Whereas Apache's processes can be restarted? /Genuinely curious
If one worker dies, any of the connections it's handling will close, but connections associated with the other worker processes stay alive. I'm not 100% sure, but I believe the master process will restart a worker if it dies.
All that said, I've never seen Nginx crash (except when playing around with an experimental third-party module - but never in production). For any production server, you should be using some form of monitoring daemon that will alert in case of a failure and automatically restart the web server process.
"Nginx uses an asynchronous event-driven approach to handling requests which provides more predictable performance under load, in contrast to the Apache HTTP server model that uses a threaded or process-oriented approach to handling requests." Does this mean if a crash occurs, the whole process of nginx will crash? Whereas Apache's processes can be restarted? /Genuinely curious
Nginx uses a configurable, fixed number of worker processes, handling many connections per worker process. This allows Nginx to maximize throughput on any variety of multi-processor and/or multi-core configurations. If one worker dies, any of the connections it's handling will close, but connections associated with the other worker processes stay alive. I'm not 100% sure, but I believe the master process will restart…
Earlier quoted context omitted.
Nginx uses a configurable, fixed number of worker processes, handling many connections per worker process. This allows Nginx to maximize throughput on any variety of multi-processor and/or multi-core configurations. If one worker dies, any of the connections it's handling will close, but connections associated with the other worker processes stay alive. I'm not 100% sure, but I believe the master process will restart…
Cool thanks for the information.
Earlier quoted context omitted.
why is your handle green?
I have no idea.
See http://news.ycombinator.com/item?id=2434333 and http://news.ycombinator.com/noobstories
Earlier quoted context omitted.
It (nginx) is bsd licensed. If you don't like the development model, you can always fork it on github, or start a company that develops and supports a closed-source fork.
Not to mention that Cherokee's configuration file format is very human-unfriendly, and its configuration utility is a GUI that requires a web browser (and port forwarding if you want to configure a server remotely, which would typically be the case outside of dev environments).