[Mongrel] Why Rails + mongrel_cluster + load balancing doesn't work for us and the beginning of a solution
gethemant at gmail.com
Thu Sep 21 15:17:42 EDT 2006
On 9/20/06, Paul Butcher <paul at paulbutcher.com> wrote:
> The real solution to the problem would be to remove Rails' inability to
> handle more than one thread. In the absence of that solution, however, we've
> implemented (in Ruby) what might be the world's smallest load-balancer. It
> only ever sends a single request to each member of the cluster at a time.
> It's called HighWire and is available on RubyForge (no Gem yet - it's on the
> list of things to do!):
> svn checkout svn://rubyforge.org/var/svn/highwire
> Using this instead of mod_proxy_balancer, and running the same test script
> above, we see approximately 54 fast and 6 slow requests per minute.
> HighWire is very young and has a way to go. It's not had any serious
> optimization or testing, and there are a bunch of things that need doing
> before it can really be considered production ready. But it does work for
> us, and does produce a significant performance improvement.
> Please check it out and let us know what you think.
(*Laziness kicks in*) How do you find...which one of mongrel id idle?
There was only one Road; that it was like a great river: its springs
were at every doorstep, and every path was its tributary.
More information about the Mongrel-users