similar to: slow first connect

I am noticing considerably longer first page load times on most of my rails apps running Rails (1.1.2) off Mongrel (0.13) on linux. After the initial request everything seems to run OK. Has anybody else noticed this and is there anyway to compensate. Also following the instructions for working with unicode from the rails wiki, the number of pages served drops noticeably. Are there any sites

Hello, For some reason when i change the "environments" line in mongrel_cluster.yml to use production, ActiveRecord Sessions stop working. Changing this line to development yield the correct result. Entries in database.yml are correct, and confirmed that the sessions table exists in both environments and that production is indeed working (production.logbeing filled up). Any idea why

since webrick does not need to run with FCGI how do you get a rails app in FCGI mode to reload the controller (since it caches in production). Is it simply a restart of apache ? adam

Hi, First of all I love Mongrel and I want to say thanks! My questions are related to how things work compared to Apache+FCGI background 1. With FCGI I would normally setup multiple FGI processes do I need to setup multiple Mongrel processes? Or is Mongrel thread based? Does the --num-procs flag work the same way? 2. Is there one database connection per process? Thanks in advance.

Hi, I''m attempting to migrate an app from Apache+FCGI to Apache+Mongrel. I''m using Apache 2.0 with the latest Mongrel release. I''m having an issue with the Mint stats package and Mongrel not picking up the following url: /mint/?js Basically inside the /mint folder there is an index.php, so the url /mint/?js should really be going to /mint/index.php?js When I had my

I am running mongrel-0.3.13.1. Have used lighty and fcgi in the past, and I must say that apache-2.0.x proxying to mongrel is much nicer to deal with! I am having this problem, however. If I am in root''s homedirectory, and start mongrel with this command: --------- mongrel_rails start -a 127.0.0.1 -e production -c /home/www/rails/myapp -l log/mongrel.log --user mongrel --group mongrel

I have posted this before with not much response so I am posing the question again. Is there a solution for this very apparent issue with mod_fcgid that the "First connection is incredibly slow". It seems its b/c mod_fcgid doesnt keep at least 1 persistent connection around that this first connection needs to start up and then every other request is fast. Is there a solution to this?

Thanks for the answer on server::start...that makes sense, just wanted to make sure I was not doing anything incorrectly. I am now running 3 mongrel servers as windows services (mongrel_cluster is not supported for windows). I have apache configured with with mod_proxy_balancer from the instructions at http://mongrel.rubyforge.org/docs/apache.html. I am able to access my app without a port

Hello, all. I released AjpRails 0.1.0. AjpRails is a script for running Ruby on Rails. Rails this script runs uses AJP13(Apache JServ Protocol 1.3) instead of CGI or FastCGI, to cooperate with your HTTPd. Its RubyForge project is: http://rubyforge.org/projects/ruby-ajp/ Project home page is: http://ruby-ajp.rubyforge.org/wiki/wiki.pl Now, AjpRails is slower and much more unstable than

Zed / List, On my workstation I''m running lighttpd 1.4.11 and mongrel 0.3.12.4. Here are my proxy settings: proxy.debug = 0 proxy.balance = "fair" proxy.server = ( "/RailsAppSample" => (( "host" => "127.0.0.1", "port" => 1337 ))) I can access http://localhost/ (default lighty welcome page) and http://localhost:1337/

Just so you know, I''ve read the manual :) http://mongrel.rubyforge.org/docs/choosing_deployment.html No php or ssl needed - that is me - simple. So I should be good to go but thought I''d ask. BTW, sorry about the stupid subject. Listening to BNL, you know ;) On 6/27/06, mongrel-users-request at rubyforge.org <mongrel-users-request at rubyforge.org> wrote: > Send

According to the mongrel_cluster.yml file you provided, you''re starting only 14 mongrels, but in your proxy balancer config you have 30 mongrels listed on ports 21000 - 21029. In this scenario, if apache tries to proxy to any ports higher than 21014 then you''ll get a proxy error as a mongrel doesn''t exist on that port. Or am I missing something? -----Original

All, I realize this was probably off-topic (not really mongrel-centric) -- my apologies. I "solved" the problem by appending to my Environment.rb: ActionController::AbstractRequest.relative_url_root = "/RailsAppSample" How come that doesn''t serve up the default "public/index.html" ? It caused a Routing Error for "", so I added a temporary

It would be an interesting topic. I bet there are quite a few. I just released one that 1/2 runs on Mongrel. http://direxionfunds.com It was released before it was _quite_ ready, but the last of the content is getting inserted today. I am still waffling on how I will leave it running longterm. Right now it uses a slightly modified version of the Mongrel http parser with EventMachine to front

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:

So, now that we''re using Mongrel and not the horrid FCGI, do I really need these files in my Rails apps: dispatch.fcgi dispatch.cgi .htaccess ?? The .htaccess file has rules for rewriting that look FCGI based. For Mongrel, I do my Apache re-writing in my config file, right? is there a reason to include these files at this point? Hunter

Hey all First off, ive just switched to using mongrel_cluster and pound - its working a treat! Its far far faster than fast-cgi: operations that took a few seconds on fcgi now are almost instant with mongrel. Excellent! However, I''ve been trying to decide how best to utilise my equipment most effectively. I have a dual pro 3Ghz Xenon with 2GB RAM, and the server will be running a few

What is the best way to determine how many mongrel daemons to launch ? right now i started with 2 under apache 2.2 with mod_proxy_balancer, but not sure how to best determine the appropriate number. adam -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060507/1640bbf8/attachment.htm

Hi, I''m trying to troubleshoot a 503 error I''m getting, my mongrels are started, mongrel.8000.log says im good to go, yet I get a 503 error trying to access it. Did a ps aux, here''s the result of that http:// pastie.caboo.se/119145, any ideas what i could be doing wrong here? My error log gives me : (61)Connection refused: proxy: HTTP: attempt to connect to

well, so File upload seems to be only working under mongrel. I have not tried it, but Camping crash extracting the request parameters on both CGI and FastCGI. I''m looking at rails code for inspiration, but it''s a bit outside of my knowledge..... not sure what to do with a FCGI::Stream object ..... this is what rails do for CGI, I''m not sure if it works the same for