Mongrel configuration

How do you know the right number of mongrel servers to run? I believe
it defaults to 3…is there a better number than 3? If so, how do you
know?

We tried 3, 10, 100… However, not sure the right setting for this
one.

anyone have any good doc that discusses this?

depends entirely on traffic. If it’s running slow and you have ram
available, increase it.

If you only get 20 hits a day you don’t need more than 1

I usually do 2 and increase it if I notice stuff going slowly (which
means most of my sites run on 2.)

thanks

Is the version of ruby important or is it fine with 1.8.5? I use to
run 1.8.6 but the new server running on CentOS came with 1.8.5 native
to the O/S. Therefore, the engineer preferred to not upgrade and let
the O/S patch. I am curious if you have any ideas about this too.

On Fri, 2008-09-05 at 05:49 -0700, David wrote:

Is the version of ruby important or is it fine with 1.8.5? I use to
run 1.8.6 but the new server running on CentOS came with 1.8.5 native
to the O/S. Therefore, the engineer preferred to not upgrade and let
the O/S patch. I am curious if you have any ideas about this too.


if it isn’t broke, don’t fix it.

Craig

On Fri, 2008-09-05 at 19:45 -0700, David wrote:

It is broke so that is why I am asking.

How many mongrel sessions should we run?

What version of ruby do you recommend?

What version of RoR seems the most stable for speed and functionality?

Is FastCGI still needed or is mongrel fine on its own?


your question on the number of mongrels was already answered…it all
depends upon the amount of traffic.

I wouldn’t recommend fastcgi any more - with mongrels, typically you use
apache as a proxy to the mongrels. The other option is to get rid of
mongrel and use mod_rails (aka passenger).

If it is broke, you haven’t offered any information to substantiate that
any change in ruby versions would be helpful.

Craig

Sorry. The problem is with performance when it hits images. It seems
the html design contains some small graphics and the redraw of the
graphics on the initial load is a bit sluggish. Therefore, I am
trying to figure out where the problem is…

The db hits are super fast and even pages without db hits run kind of
sluggish…not slow just not as fast as it should be running.

we tried 5, 10, 50 and 100 mongrel sessions. we know 50 and 100 are
a bit expensive on the servers memory. However, we wanted to see if
it made a big difference.

On 6 Sep 2008, at 20:42, David wrote:

Sorry. The problem is with performance when it hits images. It seems
the html design contains some small graphics and the redraw of the
graphics on the initial load is a bit sluggish. Therefore, I am
trying to figure out where the problem is…

If you’re doing things right, static content like images will be
handled by apache, nginx etc… (ie not by mongrel).

Fred

It is broke so that is why I am asking.

How many mongrel sessions should we run?

What version of ruby do you recommend?

What version of RoR seems the most stable for speed and functionality?

Is FastCGI still needed or is mongrel fine on its own?

On 6 Sep 2008, at 20:53, David wrote:

How do I know if apache is serving up the images? I am the RoR
developer and backend DBA and don’t know the server setup. Our server
engineer took off and now we have a new guy and he is not great with
RoR either. Any help would be greatly appreciated!

A easy way to verify this is to kill the mongrels and see if the
images are still served. if you post the relevant bit from your apache
config someone might be able to glance an eye over it.

Fred

That worked so I know it is an apache problem now…guess I need to
figure out why apache is angry! Any tips? :slight_smile:

How do I know if apache is serving up the images? I am the RoR
developer and backend DBA and don’t know the server setup. Our server
engineer took off and now we have a new guy and he is not great with
RoR either. Any help would be greatly appreciated!

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs