similar to: Multiple mongrels for one app

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:

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 tried benchmarking the same site behind an NGINX proxy with both fastcgi and mongrel, and for some reason mongrel is performing pretty poorly in comparison. Any idea what I might be doing wrong? Here''s my benchmarks for 1 fcgi: Server Software: nginx/0.4.0 Server Hostname: eship.com.br Server Port: 80 Document Path: / Document Length: 95

Is this the behavior that supposedly indicates a problem with a particular action? Mongrel in development mode randomly hangs on random actions. Further requests cause USR1 logs like: Mon Sep 18 13:04:03 PDT 2006: 0 threads sync_waiting for /, 2 still active in mongrel. Mon Sep 18 13:07:52 PDT 2006: 1 threads sync_waiting for /public/stylesheets/table.css, 3 still active in mongrel. Mon Sep 18

<% for demand in @demands %> <% cache(:action => ''list'',:part => article.id) do -%> <%= render :partial => ''article''} %> <% end %> <% end %> Under webrick,the time that list rendering costs will be very soon,but under apache2.2+mongrel_cluster, the rendering still takes a long time- which occupies about 95% of the

Howdy Folks, This release is after painstaking analysis of a memory leak that was reported by Bradley Taylor, reduced by myself, and then fixed after much work. You should all thank Bradley for finding the bizarre fix. It turns out the Ruby has a memory leak when you use pretty much any thread locking primitive other than Sync (Mutex, Monitor, etc.): http://pastie.caboo.se/10194 The fix (for

Hi all, I encounter timeout errors during file uploads in my Rails application. I think the problem may be in the Mongrel configuration. Here is my setup: * Load balancer (Cisco CSM, my provider''s Catalyst 6509) * Apache 2.2.3 with mod_proxy_balancer * Mongrel 0.3.13.3 * Rails 1.1.6 * Ruby 1.8.4 * MySQL 5.0.22 * file_column I host an application in which users may upload medium files

Hi list, I''m seeing a couple of issues with Mongrel. I''m running FreeBSD 6.1 and have previously been told that there are known conflicts between this and Mongrel, yet I hope these issues will be resolved with time. I''m overloading Mongrel with httperf on my local workstation. Mongrel is started directly with the mongrel_rails command and there is only one mongrel

Hi all, My environment is ruby-1.8.4, rails 1.2.2, mongrel 1.0.1, linux 2.6. Now, i have a problem on memory leaks with mongrel. My site is running 5 mongrel processes on a 2G RAM machine, the memory of each process grows from about 20M to about 250M, but it never recover to the initial 20M, so i had to restart the mongrel processes once per day. The load is about 1M hits per day. Waiting for

Hello Folks, This is the big release of Mongrel that''s been in the works for a while now (well, like a week). It is chock full of changes and features, but mostly it syncs up the Win32 side of things, and validates that Edge Rails works without problems. It also features a more extensive and useful example of the GemPlugins called mongrel_config. First the usual stuff for people

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

Lets say you have a site that is serving, oh, around 100k unique visitors a day (plain ole'' browser requests) - plus probably ~ 40k uniques to feeds. Assume this site is 90% read like most of the web, so the traffic looks like your typical news or portal site. There are two web boxes behind a hardware load balancer, each doing apache 2.2.3 -> mongrel_proxy_balancer -> mongrel

Hi all, I''ve been having problems with the apache 2.2-mod_proxy_balancer- mongrel setup. My setup is: CentOS 4.3 apache 2.2.3 (compiled from source) with mod_proxy_balancer mysql 4.1 ruby 1.8.4 mongrel 0.3.14 (I know I need to update but I think this problem is independent of the mongrel version) mongrel_cluster 0.2.0 rails_machine 0.1.1 I have apache setup as per Coda''s

Hello all, I''m attempting to test/tune a mongrel cluster according to the tuning instructions on the mongrel site (using httperf). Anecdotally, the site itself ''feels'' snappy, but testing it with httperf reveals what appears to be terrible throughput. I''m kind of at a loss to describe the results, and was hoping someone could verify that I''m testing

First off: Our clusters are LVS balanced Apache 2.2.3 + mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 + memcached / gem memcache_client + gem rails 1.1.6 on debian boxen, and a pgcluster backend. On 2 of our deployed clusters, we are getting the "spinning mongrel" problem. As the clusters are very low volume right now, it takes days to collect a spinner, making it

Hey everyone - I recently switched to using a Mac and have several different rails projects going and was getting tired of starting/stopping mongrels via the shell so wrote my first dashboard widget to do it for me. More details at the URL below... http://blog.pjkh.com/2006/12/20/mongrel-rails-dashboard-widget Hope those of you on OSX find it handy... feels good to finally give something

Hi- We just finished our app and I tested for performance with httperf. Our setup is browser -> apache2.2-> mod_poxy balancer-> mongrel cluster -> 3 mongrel servers. I have noticed that the total request per second is is about 7.5. When I increase the no of mongrel to 5, it inches up to 8 req/s. My question is how bad or good this number is? We are on a old dell 2400 machine

Hello, I''m running mongrel behind apache via proxypass. Every now and then, a spammer tries to proxy traffic through apache, and for some reason, apache forwards the request to mongrel, even though it''s not a site being hosted by me. At times this seems to cause mongrel to become unresponsive, and all requests to the site then fail with a proxy error until mongrel is

Hi! I''ve been following the new mongrel tuneup guide (a huge thanks for that btw) and here are my results. I''ve basically only gotten to the point where I''m tuning up 1 mongrel because I suspect I have a performance problem with my rails app. http://mongrel.rubyforge.org/docs/how_many_mongrels.html The first number is the 10s nconns and the second is the max req/s as

I''ve liked the scgi runner ever since it came out. I like the way it''scontrolled, the way it''s clusterable, and the fact that it runs onwin32 platforms so easily. Now it''s May 2006, and the scgi runner hasn''t changed since October,and now we have mongrel. I keep seeing hints of clustering in mongrel,as well. I just downloaded the win32 installer for