[delynn]

Originally Posted by mistwang

Actaully, LSAPI can be started exactly the same way by using a FCGI spawner.

I was wondering if that might not be the case. I just didn't get a chance to find/install/configure/etc the spawn-fcgi script.

Originally Posted by mistwang

However, we are thinking about a better solution by installing LSWS + ruby LSAPI on each node. As LSAPI processes are managed by LSWS directly, there is no need for spawner and spinner anymore, just let them do nothing or run "lswsctrl start" if LSWS can be started by a normal user (Not sure Capistrano can execute command as 'root' on a remote server or not?).

Only Reaper need to be changed to restart all ruby processes, I think a simple shell command "killall ruby" will do the trick (make sure ruby LSAPI 1.6 is installed). Or, just run "lswsctrl restart" if LSWS is started by a normal user.

We will release LSWS 2.2 soon, which features easy Rails configuration, should be easier than Mongrel, at least for a single server setup.

LSWS + Ruby LSAPI should give better performance on Dynamic pages as well as pages cached in file system than using Mongrel on each cluster node. I believe.

Any comments? Concerns?

Capistrano does have the capability to execute commands as a sudo user, so talking to lswsctrl shouldn't be a problem.

I'm excited to see the new features in 2.2. It sounds like there is going to be some good Rails related additions to the platform (which I think is a very smart move for LSWS). That said, I'm pretty happy with the configuration that I have right now--especially considering I'm still pretty much in development/testing mode. I think what I'm going to do is keep things as they are right now and then play around again when 2.2 is released and re-evaluate things then. From the sounds of it though, I'll be moving to LSAPI soon!

Thanks for all your help and information!

--
DeLynn Berry
delynn@gmail.com
http://delynnberry.com