[Mongrel] Deployement options

Jeremy Kemper jeremy at bitsweat.net
Wed Feb 28 15:57:02 EST 2007

On 2/27/07, Kirk Haines <wyhaines at gmail.com> wrote:
> On 2/27/07, Pete DeLaurentis <pete at nextengine.com> wrote:
> >
> > Having multiple servers has been a must in my experience with Mongrel,
> > mainly because if a task is database / IO bound then other users have to
> > wait for it.
> >
> > I'm using Lighttpd => Pound => 10 Mongrels right now.
> No, it isn't a must for Mongrel.  It may be a must for Rails, but it
> isn't a must for Mongrel.  There is a difference.  It's often blurred
> in both questions and responses, but Mongrel is far more than just a
> Rails platform.

This is true. However, his assertion is valid: it's a must for any web app
that uses blocking API calls, like executing queries using the native mysql
and postgres clients. That's just life with Ruby threads.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20070228/c91a2e6f/attachment-0001.html 

More information about the Mongrel-users mailing list