similar to: Mongrel 0.3.13 Pre-Release -- Caulking Release

We are *days* away from the official 0.3.13 release, which will be followed quickly by 0.4 code named Enterprisey Edition 1.2. This latest pre-release update closes off the last of the annoying bugs, and adds one very nasty feature people should check out before we release. Read about Katanas below. ** This release doesn''t have win32 yet. That''ll be uploaded Monday. ** WHAT

Hello Mongrel Fans, After about a Month of busy work, bad computers, moving half my house across the country, and other dramas, I''m finally pushing out the next release of Mongrel. This pre-release has lots of little goodies and the start of some documentation that should get everyone primed for the big "Mongrel 0.4 Enterprisey Edition 1.2" coming real soon now. INSTALLING

Hello Zed ! I''ve experimented a simple but limited performance tweak in the mongrel rails loader. With the following apache 2.2 mod proxy loadbalancer setup : # Redirect all non-static requests to cluster RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L] We can assume that mongrel is called only when the

Hello all, Are you aware of the rails ActionController::Base.allow_concurrency option ? If this option is true, rails is able to process simultaneous multiples actions. It appears that rails is thread-safe (if the user application is), and that this option is mostly unknown. Webrick take care of this option in rails-1.1.2/lib/webrick_server.rb at line 80 : REQUEST_MUTEX.lock unless

Hello Zed ! Do you knows or plan a way to spawn mongrel processes on demand ? I''m studying options to build an affordable but solid shared hosting solution. You wrote something very promising in your "NEXT STEPS", A combination of the ''"mostly C version'' and the mongrel_cluster replacement would be an elegant method to save much RAM on servers (until

Hi all, I''ve been spending quite a lot of time trying to install a decent RoR server on my dedicated server (Ubuntu 6.06 LTS), and now, everything works. However, the performances are not really what I had expected... I would like to know what you think about it. Here is my config: 2GHz VIA proc, 1Gb RAM, SATA-II HD. I have apt-got ruby 1.8.4, mysql5 and installed rails 1.1.4 by

I''ve been trying to track down the culprit of erratic behaviour and crashes on my production server (which is split into a number of Xen instances), so set up a staging server so that I could really try to get to the bottom of it. The staging server (also split with Xen) is set up pretty much identically as far as the mongrel_cluster server is concerned (the production box has two

Hello Windows Users! I have finally got my new computer with it''s win32 build working and have just done the first pre-release for 0.3.13 that has win32 support. *** All win32 users should try to grab the pre-release and tell me if it works. *** You can install it with: $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/ >From EITHER win32 or any other platform

Hi Folks, This is another pre-release announcement with lots of goodies for people to test and play with. At this rate the 0.3.13 release may just turn into 0.4. GETTING IT Pretty simple, just gem install mongrel --source=http://mongrel.rubyforge.org/releases/ You can get more information at http://mongrel.rubyforge.org/ WHAT''S IN IT This release has lots of little things, mostly

Hello Everyone, We''re hard at work getting the hot new win32 service Luis wrote out and ready for production. We''re hoping to have that included in the 1.0 RC1 release we make very soon. This pre-release is just to make sure that we didn''t step on any toes. Install it with: $ gem install fastthread --source=http://mongrel.rubyforge.org/releases $ gem install

Howdy Folks, This release is after painstaking analysis of a memory leak that was reported by Bradley Taylor, reduced by myself, and then fixed after much work. You should all thank Bradley for finding the bizarre fix. It turns out the Ruby has a memory leak when you use pretty much any thread locking primitive other than Sync (Mutex, Monitor, etc.): http://pastie.caboo.se/10194 The fix (for

Hi, Thanks Zed - this is very interesting. One item in particular caught my eye: Does anyone on this list have any comments or validation that Rails 1.2.1 is 2-4 times as slow as Rails 1.1.6? Topfunky provided a link that purports what looks like really horrible performance and memory characteristics for Rails 1.2.1, even v. 1.1.6:

Yo Zed, Just curious -- what do you think of the LiteSpeed server? Is it better than Lighty? Does it (gasp!) also serve Rails apps like Mongrel? I think I read that LiteSpeed doesn''t have proxying support. Thanks, Joe __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Hi, I just found something weird for mongrel with static files. Performance endlessly decreases if mongrel serve static files from simultaneous requests : Here is the test setup: Ruby on Rails Mongrel (tested with 1.3.12.4 and 1.3.13-pre installed today) Ubuntu dapper, compiled ruby 1.8.4. http client : while true; do ab -n 1000 -c 30 http://localhost:3000/ 2>/dev/null | grep

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

Just a quick note for a few new features/fixes available on the Mongrel pre-release and a new document that covers nearly all the big features and configurations for Mongrel. First, the document is http://mongrel.rubyforge.org/docs/howto.html and it covers: * All the start command options including the fresh -G option to generate a config for -C. * The format and usage of the MIME type file (-m

Howdy Folks, This release is after painstaking analysis of a memory leak that was reported by Bradley Taylor, reduced by myself, and then fixed after much work. You should all thank Bradley for finding the bizarre fix. It turns out the Ruby has a memory leak when you use pretty much any thread locking primitive other than Sync (Mutex, Monitor, etc.): http://pastie.caboo.se/10194 The fix (for

Hey Folks, I''ve been holding off the official 0.3.13 release so that Luis can get the win32 side very nice and clean. We fixed a major problem last night so it''s only a short time before we get it out. Luis is working really hard on it, so just be patient. In the meantime, I''ve been doing a code audit of the Mongrel code as it is now and fixing any little things I

Hi Folks, As you can tell we''re getting closer to the 0.3.13 release being official. There''s a new pre-release available for non-win32 users: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Which has the following fixes and enhancements: * Rewritten internal HTTP processing to protect against trickle attacks. This means that a client can send one byte

Hello Folks, There''s another update to the Mongrel pre-release that fixes a small bug with the --version options to commands, and adds a new "version" command. Please update with: $ gem uninstall mongrel $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/ And continue reporting problems to me. -- Zed A. Shaw http://www.zedshaw.com/