From: Tobias Luetke <tobias.luetke@...>
Date: 2005-03-24T07:30:01+09:00
Subject: Re: need Rails advice

Mod_ruby, while supported, is not much of an option. 

There are the fundamental problems with its architecture like
in-process ruby interpreter which for a rails application means you
will run around with 20mb baggage per apache worker process. Apache
loves to start a lot of worker processes so you have to take this into
account when buying ram.

However thats only the small reason against it, the big is that you
can only run one rails application on your apache installation since
the ruby processes are shared.

Fastcgi solves all this, it creates a pool of rails applications which
handle the requests coming to it and you can dictate the maximum size.
Fastcgi is also a whole lot faster.

I recommend lighttpd as web server. 


On Thu, 24 Mar 2005 07:01:22 +0900, Chris Newman
<Chris.Newman@dalsemi.com> wrote:
> I have inherited an existing intranet web server that runs Apache 1.3 on
> Solaris 8. It is a bit limited so I am putting together a development web
> server to test various Apache modules, Content Management Systems, etc. The
> new server will run Apache 2.0 on Solaris 8. I was interested in trying Ruby
> and perhaps even Ruby on Rails and I have a couple of questions...
> 
> Should I use mod_ruby or fastcgi?
> Will there be a significant performance difference depending on which I
> choose?
> Will Rails work with both?
> 
> Thanks in advance for any advice,
> 
> Chris
> 
> 


-- 
Tobi
http://www.snowdevil.ca - Snowboards that don't suck
http://www.hieraki.org   - Open source book authoring
http://blog.leetsoft.com - Technical weblog