From: Curt Sampson Date: 2007-12-27T00:36:31+09:00 Subject: Re: Looking for a new web framework. On 2007-12-14 11:15 +0900 (Fri), Ben Bleything wrote: > On Fri, Dec 14, 2007, Tim Uckun wrote: > > What is the state of mod_ruby these days? Is it robust? Why is it that > > rails, merb, etc don't run on it? > > ...there are a lot of reasons why it's not in common use these days. Rails > supported it (maybe still does) early on, but it didn't work that well > because each Apache child has its own interpreter that is persistent... > contrast this with FCGI (for instance) where the state is effectively > cleared between requests. FCGI has persistent state between requests as well. One issue with mod_ruby might be that a Ruby interpeter really, really likes memory, and Apache, at least in fork mode, really likes a lot of children. Sixty apache children, each with a long-lived Ruby interpreter, can eat up a couple of gigabytes of memory pretty quickly. With lighttpd and Ruby FCGI backends, on the other hand, I find I tend to run fewer Ruby interpreters (a dozen, maybe sixteen on a reasonably busy site) because once the request is complete, the FCGI backend is freed to process the next request even while the lighttpd is still waiting for the client to accept the data. cjs -- Curt Sampson +81 90 7737 2974 Mobile sites and software consulting: http://www.starling-software.com