search for: paulrabutcher

...red production ready. But it does work for us, and does produce a significant performance improvement. Please check it out and let us know what you think. -- paul.butcher->msgCount++ Snetterton, Castle Combe, Cadwell Park... Who says I have a one track mind? MSN: paul at paulbutcher.com AIM: paulrabutcher Skype: paulrabutcher LinkedIn: https://www.linkedin.com/in/paulbutcher

...#39;d like to get it to output to syslog. Our Rails apps already do this (via SyslogLogger) - is there any way to persuade Mongrel to do the same? Thanks! -- paul.butcher->msgCount++ Snetterton, Castle Combe, Cadwell Park... Who says I have a one track mind? MSN: paul at paulbutcher.com AIM: paulrabutcher Skype: paulrabutcher LinkedIn: https://www.linkedin.com/in/paulbutcher

...hanks in advance for any help you can offer! ------------------------------------------------- Paul Butcher CTO RE5ULT Limited 74 Eden Street, Cambridge CB1 1EL http://www.82ask.com/ Office: +44 (0) 1223 309080 Mobile: +44 (0) 7740 857648 Email: paul at 82ask.com MSN: paul at paulbutcher.com AIM: paulrabutcher Skype: paulrabutcher LinkedIn: https://www.linkedin.com/in/paulbutcher ------------------------------------------------- 82ASK: text any question to 82ASK (82275) and get the answer in minutes. Visit www.82ask.com to get your first 2 questions answered for free.

Hello! Today I''m announcing a "soft but official" release of Mongrel 0.3.13.4 for the Unix fans in the crowd. It''s been running stable for quite some time now for many people, and should be great for nearly everyone. You can read the announce at: http://mongrel.rubyforge.org/ This release includes new versions of mongrel_upload_progress and mongrel_cluster.

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

Morning Folks, As most of you know there were a few people who had the following three bugs: * CLOSE_WAIT: Lots of sockets in CLOSE_WAIT state. * 99% CPU: Mongrel''s getting "stuck" pegged at 99% CPU. * LEAK: Memory leak. I''ve successfully fixed these bugs or attributed them to one main cause: pstore. First, the memory leak was because of a bug in how the GC in Ruby