similar to: How to improve my response speed?

A small note to all the FreeBSD folks about Ruby performance. While trying to tune Mongrel to run faster on FreeBSD I was stumped as to why it was so horribly slow compared to Linux. Linux on the same machine was getting about 800 req/sec, and FreeBSD was maybe pushing 23 req/sec. Pathetic. I managed to tweak the thread model in Mongrel and get FreeBSD up to about 210 req/sec but still that

Bradley Taylor shot me this *goldmine* of ugly ugly ugly dogs: http://www.sonoma-marinfair.org/uglydogvote.shtml I *have* to use one of these for the Mongrel BUGS Mascot. He''ll go on our bug list page and replace the little beetles on the left. Pick the dog you think best represents a lovable but defective pooch and reply to this with your +1. Let the voting begin! -- Zed A. Shaw

Hi all, I have a rails app running on mongrel on freebsd using mongrel 0.3.13.3 with ruby 1.8.4. Mongrel dies every time the application generates an exception. I have the same setup running on a linux box without any problems. Mongrel crashes with the following error: Bus error (core dumped) And the following message in /var/log/message kernel: pid 57638 (ruby), uid 0: exited on signal 10

I would like first to introduce my self to the community. I am Steve Beyer and I am interested in learning Ruby, ROR, and how to set up a production server. I am going to use OSX for my client/developement system but I would like to get some advice on what operating system you would recommend for a production server. I want to use Mongrel to start and then move up the ladder as my

Following errors are taken from monrgrel running in development mode. It complained routes.rb, no such file or directory and then sometimes i get application.rb, no such file or directory.Doesn''t seem correct to me. Though not so often, but even production servers throw these errors sometimes, and i have no special routes setup or something.Its pretty much default one, except few changes

Hello Everyone, Mongrel is due for a 0.3.12 release which will feature some pretty insane goodies for everyone. There''s talk of IOWA support, lots of speed improvements (including sendfile support), a great Configurator which makes configuring Mongrel a snap (especially for framework implementers), and a ton of debugging stuff. WARNING This is a pre-release announcement for the

I have been trying to set up Hieraki 2.0.1 and I cannot seem to get it running. I am running on FreeBSD 5.4, Ruby 1.8.4, Apache 2.0.55, Mysql 4.1.16, ruby-mysql 2.7, mod_scgi 1.9, scgi_rails 4.3 and Rails 1.0. I can start up the wiki, get it to display the home page, and when I click on the signup link the signup form displays. When I fill in the signup form and click the signup button, the

If this was in the docs, I''ve missed it. How can I have multiple mongrel clusters on a server? All the documentation that I am seeing seems to assume that I am only running one cluster.

Hi, I can''t install Mongrel on Ruby 1.8.6 (patchlevel 279), using Windows XP. My environment: C:\ruby18>gem environment RubyGems Environment: - RUBYGEMS VERSION: 1.2.0 - RUBY VERSION: 1.8.6 (2008-07-17 patchlevel 279) [i386-mingw32] - INSTALLATION DIRECTORY: c:/ruby18/lib/ruby/gems/1.8 - RUBY EXECUTABLE: c:/ruby18/bin/ruby.exe - EXECUTABLE DIRECTORY: c:/ruby18/bin -

I''m running FreeBSD 6.1 and installed the 1.0.1.1 mongrel_cluster prerelease. I had a problem with the mongrels not stopping, and it turns out it''s because ps is reporting my processes as just [ruby18] instead of someting more like "mongrel_rails start -d ......." Not sure why it''s doing that, but it is. Any ideas? For the time being I just changed line

We tried to give Mongrel a go running our application which has moderate traffic. We got mongrel up and running easy enough but 3 times in a short period(2hours) mongrel just died with the following error when we went live to production with it. As you can see we are running mongrel-0.3.13.3. /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:576:in`peeraddr'': Transport endpoint

Hey folks. Sorry for the SUPER long email but if you''ve been experiencing the same problems with restarting your mongrel cluster with Capistrano, then I have two solutions that have worked for me and I''m pretty sure will for you as well. THE PROBLEM I was having trouble restarting my clusters using Capistrano. I''ve seen this come up before on the mailing list and

Hi there, We''ve been using previous version of bdrb (drb based one) for a while and it was running relatively OK. We recently attempted to upgrade to the new version to keep up / use supported version but we ended up reverting to the older version. Here are the things that moved us to revert : 1) With the workers we never manage to pass this error: '''' You have a nil

I''ve been troubleshooting this problem for several hours now and haven''t been able to figure out what''s wrong. I have two boxes, dev and prod, both are identical except that prod uses Ruby 1.8.5 and dev uses 1.8.4. Both are running Slave 1.2.0, Daemons 1.0.5, and Backroundrb 0.2.1. The behavior I''m seeing is this. When I first start Backgroundrb, this is what

I was able to find some information about this in the list archives, but it ended with a possible patch being submitted for Mongrel. I tried to follow a few of the instructions, but I''m still kind of stuck, since I''m not sure if what I''m seeing is the proper results. I have an application running on a cluster of mongrel servers, which is behind pen, which in turn is

Hi Y''all, Just a quick note announce an update to mongrel_cluster. Changes: - ''mongrel_rails cluster::restart'' now calls ''mongrel_rails stop'' and ''mongrel_rails start''. ''cluster::restart'' now accepts the ''force'' argument instead of ''soft''. - Added ''.conf'' as

Hi y''all; A quick note to announce the release of mongrel_cluster, a gem_plugin for Mongrel. This plugin provides commands for managing multiple Mongrel processes behind a reverse-proxy server and load balancer. To install: gem install mongrel_cluster Configure (use -h to options): mongrel_rails cluster::configure Start: mongrel_rails cluster::start I''ve posted a quick

I posted this to the rails list before by mistake, and only later realized that there is a specific mongrel list. Uff, I got lost. I had mongrel_cluster 0.1working fine, even with capistrano (my own hack). Then came mongrel_cluster 0.1.1 and I tried to set it up, but somehow I messed up things and nothing worked anymore. So here is what I did: on production machine: (debian linux, rails 1.1)

Hello... I am trying to switch to mongrel from webrick to get rid of the . puppetmaster is FreeBSD 6.2 with ruby, puppet, and mongrel all from ports (latest as of this morning). I get "Server is not a class". --verbose, --debug do not spit out any useful info. puppet-0.22.4 ruby-1.8.6.111_1,1 ruby18-bdb46-0.6.2 ruby18-gems-0.9.4 rubygem-daemons-1.0.8 rubygem-fastthread-1.0

Anybody know where to submit a bug for mongrel_cluster. Thanks _________________________________________________________________ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement