Jarkko Laine wrote: > Mongrel is a standalone ruby program, so yes, it is a server. It > loads the Rails code on startup just like a FastCGI process does. You > can use it by itself as a web server just like webrick. However, the > normal use is to use a web server like nginx, lighttpd or apache in > front of multiple mongrels as an http proxy. In that case the setup > is similar to the FastCGI setup, with the exception that the frontend > server uses http to connect to mongrel instead of unix sockets. For > that reason you can also use a load balancer like pen, pound or > haproxy directly in front of the mongrels. > > Mongrel's speed is in the same ballpark as FastCGI's with Rails (it > is, after all, a similarly long-running process). It might be a tad > slower because sockets are probably a bit faster than going through > http. However, the difference is normally negligible and will be more > than offset by the flexibility it brings you. There have also been > some stability problems with the FastCGI approach which are > exceedingly harder to debug than plain http connections.
Thank you, this explanation was very useful. I have used Mongrel on my local computer (as you mentioned just like you use Webrick). But I'm really interested in the real-life use of Mongrel... So the setup would be: Apache (as reverse proxy: http://en.wikipedia.org/wiki/Reverse_proxy) with one or more Mongrel servers behind it. What does Apache handle? Static requests? Or does it pass every request to a Mongrel server, so that it exclusively acts as a proxy? -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
