Comments on: Potential problems with preforking Ruby on Rails http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/ Ecchi nanowa ikenai to omoimasu Sat, 05 Jul 2008 18:35:52 +0000 http://wordpress.org/?v=2.3.3 By: Hongli http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-7452 Hongli Thu, 06 Dec 2007 20:57:50 +0000 http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-7452 Jenn, what "potential risks" are you talking about? Forking is a well-known and well-understood concept. Whatever problems that may arise are simply implementation issues that can be fixed. It's not black magic. Jenn, what “potential risks” are you talking about? Forking is a well-known and well-understood concept. Whatever problems that may arise are simply implementation issues that can be fixed. It’s not black magic.

]]> By: Ruby Developer http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-7449 Ruby Developer Thu, 06 Dec 2007 19:16:24 +0000 http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-7449 I don't think there are potential risks are worth it. Let's stay away from Forking people, unless you want to spend endless nights of Christmas fixing stuff. Jenn I don’t think there are potential risks are worth it. Let’s stay away from Forking people, unless you want to spend endless nights of Christmas fixing stuff.

Jenn

]]> By: Ruby Garbage Collection Links « Open Source Teddy Bears http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6524 Ruby Garbage Collection Links « Open Source Teddy Bears Mon, 25 Jun 2007 07:44:48 +0000 http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6524 [...] * Hongli Lai [...] […] * Hongli Lai […]

]]> By: Hongli http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6504 Hongli Tue, 29 May 2007 23:02:22 +0000 http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6504 What I do is forking before any requests (but after Rails has been loaded). Wouldn't that solve all problems? What I do is forking before any requests (but after Rails has been loaded). Wouldn’t that solve all problems?

]]> By: Marcin Raczkowski http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6503 Marcin Raczkowski Tue, 29 May 2007 20:41:59 +0000 http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6503 problem with database connections is that when you try to do 2 gueries CONCURENTLY two processes use same descriptor which can cause unexpected behavior - i'm currently working on fixing that isue with my mongrel modiication - it should allow mongrel to fork on request, i'm using your script for preloading - and i'm going to release my modifications on compatibile OS license greets Marcin Raczkowski problem with database connections is that when you try to do 2 gueries CONCURENTLY two processes use same descriptor which can cause unexpected behavior - i’m currently working on fixing that isue with my mongrel modiication - it should allow mongrel to fork on request, i’m using your script for preloading - and i’m going to release my modifications on compatibile OS license

greets
Marcin Raczkowski

]]> By: HelloWorld http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6456 HelloWorld Sat, 28 Apr 2007 10:07:49 +0000 http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6456 Peace people We love you Peace people

We love you

]]> By: Hongli http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6396 Hongli Thu, 05 Apr 2007 23:40:57 +0000 http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6396 Oops, you're right, I forgot to disable reloading of classes. I've fixed my blog post now, thank you for pointing this out. :) The memory savings turned out to be far better than expected: from 55% to 75%! Oops, you’re right, I forgot to disable reloading of classes. I’ve fixed my blog post now, thank you for pointing this out. :) The memory savings turned out to be far better than expected: from 55% to 75%!

]]> By: Ezra http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6395 Ezra Thu, 05 Apr 2007 22:01:52 +0000 http://izumi.plan99.net/blog/index.php/2007/04/05/problems-with-preforking-ruby-on-rails/#comment-6395 With the rails config settings you showed in your last post: config.cache_classes = false config.whiny_nils = true config.breakpoint_server = false config.action_controller.consider_all_requests_local = true config.action_controller.perform_caching = false config.action_view.cache_template_extensions = false config.action_view.debug_rjs = false You are basically running in development mode which means rails does a lot of reloading of classes and db handles on each request. In production mode this does not happen. Please use a standard rails production mode config with caching turned on and try your experiments again. I'm interested to see what you find out. With the rails config settings you showed in your last post:

config.cache_classes = false
config.whiny_nils = true
config.breakpoint_server = false
config.action_controller.consider_all_requests_local = true
config.action_controller.perform_caching = false
config.action_view.cache_template_extensions = false
config.action_view.debug_rjs = false

You are basically running in development mode which means rails does a lot of reloading of classes and db handles on each request. In production mode this does not happen. Please use a standard rails production mode config with caching turned on and try your experiments again. I’m interested to see what you find out.

]]>