similar to: Memory leaks in my site

Hi -- I have been reading documentation and googling around to find the correct way to do this but I have found many ways that seem to not work, or the documentation makes no reference to. I am using mongrel cluster with 10 mongrels for each server. Recently I installed monit but which lead me to find the correct way to start/stop mongrel instances one pid at a time. I am assuming one pid at a

Hello, I''m running a Rails application which must sort and manipulate a lot of data which are loaded in memory. The Rails app runs on 2 mongrel processes. When I first load the app, both are 32Mb in memory. After some days, both are between 200Mb and 300Mb. My question is : is there some kind of garbage collector in Mongrel? I never see the two Mongrel processes memory footprint

Hi, I was wondering if this is normal or if it something i need to wonder about. I get Monit alerts that my mongrels PID files have changed. Changed Service MONGREL_2 Date: Tue, 09 Oct 2007 14:19:38 +0000 Action: alert Host: sa.greenling.com Description: ''MONGREL_2'' process PID changed to 18368 Your faithful employee, monit

Is there anything mongrel cluster gives you that monit doesn''t? I''ll be using monit to monitor a number of other services anyways, so it seems logical to just use it for everything including mongrel. Chris

Dear all, I am researching solutions for "how do you squeeze as many Rails apps as you can on a cluster" problem. Environment constraints are as follows: * 4 commodity web servers (2 CPUs, 8 Gb of RAM each) * shared file storage and database (big, fast, not a bottleneck) * multiple Rails apps running on it * normally, the load is insignificant, but from time to time any of these apps

I''ve been trying to track down the culprit of erratic behaviour and crashes on my production server (which is split into a number of Xen instances), so set up a staging server so that I could really try to get to the bottom of it. The staging server (also split with Xen) is set up pretty much identically as far as the mongrel_cluster server is concerned (the production box has two

Alright, I have googles and read through the docs on monit I get this error when adding -v starting monit monit: Cannot connect to the monit daemon. Did you start it with http support? monit: Cannot connect to the monit daemon. Did you start it with http support? Am I missing something here? set daemon 120 set logfile syslog facility log_daemon set mailserver localhost set httpd port 28212

Hi All, I am new to the mongrel mailing list and I have a question (and I didn''t find any answer in the archives). I have successfully installed the apache2.2 proxy balancer with mongrel cluster and that works just fine. For a single rails app I have started 2 mongrels which consume about 100M (ps says 5.0% for each and I have 1G RAM). It seems a bit much but OK. However that would

Hello Mongrels, Building on the last messages about Fastthread, can we get a detailed survey of the different ways people are deploying their applications? It will help with near-future Mongrel development. Please include the following things: * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, Rack...) * Mongrel version * Mongrel handlers used (rails, dirhandler, camping,

Greetings - I dug around a bit and I couldn''t find a definitive answer to this question, apologies if it''s been covered before. A box running a apache 2.2 -> mongrel cluster for a rails app got power cycled at my ISP. Unfortunately monit couldn''t start the mongrel processes because the pid files were still there. Here is my monit config (for each mongrel

Hi all: New to the list. Im enjoying mongrel. Coming from a background of weblogic clusters this is a dream. However I have a few questions: I have used HTTPerf to analyze metrics for an application ( rails ). My question pertains to the CPU utilization threshold: 1) Test with single mongrel server : sustained cpu util @ 98% 2) Test with 2 mongrel nodes in a mongrel cluster with apache and

Hi, I''ve done some benchmarking on our new servers (being built now), AMD X2 5600, gentoo-hardened. With the same CFLAGS (safe cflags: -march=k8 -O2) I''ve tested the following configs: 1, emerge ruby rubygems, then gem install mongrel (or emerge mongrel, the performance was similar) 2, download the same ruby version, untar, ./configure, make, make install, download rubygems,

I''m trying to do some initial benchmarking of our setup, mainly just to establish baselines. I''m essentially using the process Zed outlines in a previous message: http://rubyforge.org/pipermail/mongrel-users/2006-May/000200.html What I''m running into is that Mongrel appears only half as fast as Apache when serving a small static HTML file. If I then add in Apache with

I have Mongrel Cluster setup with Apache a mod_proxy_balancer. I''ve seen (from time to time) mongrel instances become non-responsive. Is there anyway to configure the balancer so that it "knows" which processes are no longer good and stops trying to use them? _______________________________________________________ The FREE service that prevents junk email

Dear all, If you thought Instiki was a dead project, you were right. Since I''ve got a day job that doesn''t suck (Official Ruby Zealot of ThoughtWorks Canada), my motivation to do open source greatly sufferred :) But... but... but! Here is Instiki 0.11.0, and in this version Instiki is (finally!) moving to ActiveRecord backend and (finally!) has the File Upload feature.

is there a way to determine how best to determine the number of mongrel processes to start? Right now i am running 2 in production but I see some people run about 8 or so. What is the cutoff and determening factor for this ? thanks adam -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello all, So, I''ve been using monit with mongrel for a while now, since the 0.3.x days (I think it was). It used to work fine, but now I seem to be having some trouble. I''m currently using mongrel 1.0.1 and I am using the same monit configuration I''ve always been using, yet everytime monit should restart mongrel, I get "Execution failed". For the start

Hello all, I''m new to Mongrel and am very impressed with what I see so far. This thing beats FastCGI hands down, and is even simpler to use than SCGI. Great job Zed! Thanks for all the hard work. I am a bit surprised at the memory usage patterns though. I''m not sure if I''m doing something wrong (most likely I am), or if this is a problem with the app I''m

If (like me) you use ccrb to test a Rails app and (like me) you define your own :cruise task, because, for example, you use rspec rather than Test::Unit and (like me) you have the RAILS_ENV ||= ''production'' line in environment.rb (because, like me, you use crummy shared hosting) Your build will run in production mode, possibly screwing up your production database,

Hello all. I too found out that I sometimes have some action that can take up to 10 seconds in my rails application. I''ve read all arguments Zed made about polling/and inbox strategies, and I think I just can''t work around my feeling that a "wrong" request that takes up too much time should be able to lock subsequent requests in mongrels queue. That''s what