search for: mod_proxy_balanced

I''m trying to setup a mongrel cluster. I''m relying on information collected from a number of sources but I''m relying heavily on http://mongrel.rubyforge.org/docs/apache.html. I have noted that a number of sources mention the necessity of having the mod_balancer module installed in Apache. However, my primary source makes no mention of this; but instead, mentions only

Rails instances themselves are almost always single-threaded, whereas Mongrel, and it''s acceptor, are multithreaded. In a situation with long-running Rails pages this presents a problem for mod_proxy_balancer. If num_processors is greater than 1 ( default: 950 ), then Mongrel will gladly accept incoming requests and queue them if its rails instance is currently busy. So even

Hello list, I wonder if someone could help me understand the following: I''ve got a managed dedicated server with GoDaddy. Until now, I''ve only hosted PHP applications there. I now need to set it up to host my new beloved Rails application. I asked them to set up apache with mod_proxy_balancer for the mongrel cluster, however, here''s what they told me: *Unfortunately,

Cheers, I''ve just published a blog post about scaling Rails with Apache 2.2, mod_proxy_balancer and Mongrel. This way you do not need another proxy server or load balancer for Mongrel. Just use Apache 2.2 and mod_proxy balancer. http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel Jonathan -- Jonathan Weiss

more info just 1 server webserver + appserver + dbserver On 9/14/07, Yan Meng <dreamwords at gmail.com> wrote: > > Hi, Guys > > Our team is running a web2.0 finance site in China > > http://www.caibangzi.com/ > > We use APACHE + mod_proxy_balancer + mongrel to deploy our application, it > workd super in the past few monthes. > > However, just from last

Our Mephisto install kills Mongrels and causes Apache to pound the CPU. This started when we moved to Apache+mod_proxy_balancer+Mongrel. Here''s what we know: The following things are working OK, except when used in the combination listed above: mongrel, mongrel_rails, MySQL, Apache, mod_proxy_balancer. We believe these are all OK because we moved five other Rails apps to this

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

Hello everyone- I am considering using Mongrel and I have read this list pretty extensively. I know that the Apache/mod_proxy_balancer/mongrel approach is the preferred one right now, with Apache serving the static content via mod_rewrite and such. However, in my hardware arsenal, I already have an old and trusty LocalDirector, which I would be inclined to at least try first as a

Try nginx + evented mongrel instead of apache + normal Mongrel. Maybe :) -Roger -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20070917/c6f6f43a/attachment.html

I''m newbie to mongrel, I''m not able to config mongrel_cluster in order to host multiple web sites added/remove as apache VirtualHost. I followed codahale http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ mixed with Wiki Radiant (I use Radiant as a rails apps to be deployed, 1 domain 1 radiant sites with its own document tree

Hello all, My Rails app is logging some rather strange requests: Processing StoreController#index (for ::1 at 2006-07-03 13:18:48) [GET] Session ID: ed5e2a0e5b4b9290835a969cdd749e6e Parameters: {"action"=>"index", "controller"=>"store"} Completed in 0.08174 (12 reqs/sec) | Rendering: 0.07951 (97%) | DB: 0.00000 (0%) | 200 OK [http://127.0.0.1/]

I started the mongrel_cluster and tried to use the RewriteRule to forward the requests to proxy_balancer just as the http://mongrel.rubyforge.org/docs/apache.html said. When I visited my site from a remote computer, I always got the error messages "Forbidden, You don''t have permission to access / on this server." Finally, I added the "Allow from all" property (in the

> On 5/23/06, Walter <Walter at mwsewall.com> wrote: > [...] > > I realize that mongrel is not thread safe, I was hoping mongrel might > spawn a few processes and serve them in the background to emulate what I > wanted. > > > > Rails is not thread-safe. > Yes, that?s what I meant. <snip> > > The idea of the BackgroundDrb is that you perform

Is anyone using ferret with Mongrel/Mongrel-cluster? The first one or two times I access the ferret index it works fine, but then it throws a write lock error StandardError (: Error occured at <index_rw.c>:703 Error: exception 6 not handled: Could not obtain write lock when trying to write index ): I need to do more testing on this to narrow down the problem/solution but just wanted to

I recently moved an app. from lighttpd + fastcgi to apache 2.2 + mod_proxy_balancer + Mongrel. On lighttpd, I was using basic authentication with a configuration like this: auth.backend = "htpasswd" auth.backend.htpasswd.userfile = "/path/to/htpasswd" auth.require = ("/" => ("method" => "basic", "realm" => "My

I''d like to implement output compression in Mongrel (ala Apache''s mod_deflate). I have found a Rails plugin that, with minor modification, works. Is there even an advantage to moving the output compression from the Rails app to a Mongrel handler? Unless, of course, someone knows how to configure mod_proxy_balancer with mod_deflate... == Will Green Web Developer & IT

Gang- We are getting ready to launch our ROR application; the last item remaining is the deployment platform. For testing, we had used Apache + MOD_FastCGI. I am not that impressed with it; sometimes it has strange effects. For example, when we start the application, for about 5 minutes or so, the app is very unstable and it gets better over time. My questions is .. should I go with (1)

I am using mongrel_cluster with mod_proxy_balancer and would like to enable compression (assuming it improves throughtput) and limit file size upload. I configured mod_deflate and LimitRequestSize in Apache, but in my trials looks like the proxied calls bypass those directives (the conf goes below). Is there a way to get this? -- fxn # Adapt this .example locally, as usual. # # To be

I am using Apache2.2 + mod_proxy_balancer + mongrel setup and my mongrel.conf file(for apache is like this) 2 3 <Proxy balancer://mongrel_cluster> 4 BalancerMember http://127.0.0.1:9000 5 BalancerMember http://127.0.0.1:9001 6 BalancerMember http://127.0.0.1:9002 7 </Proxy> 8 9 <VirtualHost *> 10 ServerAdmin rags at

We have been searching for a Rails deployment architecture which works for us for some time. We''ve recently moved from Apache 1.3 + FastCGI to Apache 2.2 + mod_proxy_balancer + mongrel_cluster, and it''s a significant improvement. But it still exhibits serious performance problems. We have the beginnings of a fix that we would like to share. To illustrate the problem, imagine a