> We've experimented a bit with a LiteSpeed/LSAPI combo for hosting as > many Rails apps as possible w/o overcrowding. LiteSpeed seems to have > a couple of features particularly favorable for this sort of setup: > * It will start w/ one LSAPI process, but scale up and down > dynamically as necessary, up to a specified limit > * You can set resource limits at the web server level on your LSAPI > processes > > So far, our experience has shown us that LiteSpeed/LSAPI works great > for running a lot of small sites on a single server, and is dead- > simple to set up (LiteSpeed comes with a web-based admin which allows > you to do most of the legwork of setting up new sites). However, > LiteSpeed did not work well for us for larger applications. For that, > we still use good 'ol Apache/Mongrel.
Chris - Can you share what issues you had for larger apps? And was that with their 2.x or 3.x server? At work we've got a couple of the servers running litespeed and a couple apache/mongrel and so far haven't noticed any issues... but maybe are apps are different.. Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
