On Jan 4, 2:59 pm, "Ericson Smith" <[EMAIL PROTECTED]> wrote:

> It seems that you still have to manually start Swiftiply processes as your
> traffic scales. You set the mins and maxes and litespeed does it for you.
> This is what I meant by not having to worry about the web serving deployment
> aspect of your application.

The problem with auto start scaling is that it destabilizes the
environment. I don't mean that you'll crash more, but that your
performance will change over time, and sometimes in ways that you
might not predict.

For high volume sites, you want to bring up the system initially into
an optimal state, and then keep it there, IMHO.

Auto starting processes is good for low end stuff, but not really
applicable to high volume sites

> Swiftiply does still seem like the answer to some of the large issues with
> mongrel though. Based on my cursory reading of the site, it still seems that
> you will have the problem of stopping/starting/restarting processes though.
> Lets face it, our Rails apps will from time to time have memory leaks and
> crash their containers. You may be lucky to write the perfect app that does
> neither, but in my experience, this is a pretty common thing.
>
> Having something that manages that aspect is a no brainer.

You can use monit or god to monitor those processes. One advantage of
this method is that you only need to make sure your process monitor
starts automatically at startup, and then it will handle starting the
application servers too. This is, of course, exactly the same behavior
as LightSpeed, so I'm not claiming advantages here.

We'll soon be releasing an open source plug-in for nginx called "nginx
fair proxy" that using a much improved proxy algorithm that limits the
number of connections nginx will open against mongrel. We've seen far
better performance, and much less mongrel bloat on high volume sites
during our testing.

nginx + mongrel ++ (with or without evented mongrel)

Also, take a look at merb with datamapper for applications that need
really high performance.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to