search for: evented_mongrel

I heard about a new mongrel plugin or version that''s single threaded and uses non-blocking IO with events. It''s called something like "swifty fly". Anyone have a link for it? Thanks.

I read this in a previous post ( http://rubyforge.org/pipermail/mongrel-users/2006-December/002354.html) .... First, Mongrel accepts remote clients and creates one Thread for each request. Mongrel also enforces a single request/response using Connect:close headers because Ruby only supports 1024 files (so far). If Mongrel doesn''t do this then people like yourself can write a simple

Hello, I''m running a Rails application which must sort and manipulate a lot of data which are loaded in memory. The Rails app runs on 2 mongrel processes. When I first load the app, both are 32Mb in memory. After some days, both are between 200Mb and 300Mb. My question is : is there some kind of garbage collector in Mongrel? I never see the two Mongrel processes memory footprint

Has anyone had troubles from Mongrel > 1.0.1? Just curious, because the last time I tried to run Merb it gave me some Mongrel error about the wrong number of arguments, or something like that. I can post the exact message tonight when I get home. -- Cheers, Kevin Williams http://kevwil.com/ http://www.almostserio.us/ http://kevwil.jaiku.com/

Just a quick announcement that an update to swiftiplied_mongrel and evented_mongrel which fixes the incompatibility with Mongrels > 1.0.1 has been released. http://swiftiply.swiftcore.org Let me know if you have any problems. Kirk Haines

Sorry if this is the wrong place to ask, but when I run mongrel evented using swiftiply and then send it the USR2 signal to restart it, it dies. Without eventing, USR2 restarts mongrel as expected. Anyone else seen this? Here''s a dump: $ EVENT=1 mongrel_rails start -d -P /tmp/m.pid -p 4321 Using Evented Mongrel ** Ruby version is up-to-date; cgi_multipart_eof_fix was not loaded $ kill

Hello, I''m trying to run the latest/greatest mongrel version: % sudo gem install mongrel ... Successfully installed mongrel-1.1 % gem list mongrel mongrel (1.1) % ruby -v ruby 1.8.4 (2005-12-24) [powerpc-darwin7.9.0] % uname -a Darwin NewYork.local 7.9.0 Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC Power Macintosh powerpc

Hello. I have discovered that mongrel does not correctly take on all the groups of the requested user/group combination. It seems that while the specified user and group is correctly activated, all the other groups that are associated with this user are not enabled and the group permissions remain the same as the caller (i.e. root). This problem (and solution) is discussed in the Ruby Forum:

So here''s a random question: if a (Ruby) multi-threaded rails server could exist (bug free), would it be faster than using a mongrel cluster? (I.e. 10 mongrel processes versus 10 Ruby threads). I''m not sure if it would. RAM it might save, though. Any thoughts? -Roger -------------- next part -------------- An HTML attachment was scrubbed... URL:

Sorry, for the re-post, but I''m new to the mailing list and wanted to bring back up and old topic I saw in the archives. http://rubyforge.org/pipermail/mongrel-users/2008-February/004991.html I think a patch to delay garbage collection and run it later is pretty important for high performance web applications. I do understand the trade-offs of having explicit vs. implicit garbage