On Mon, 24 Mar 2008 08:21:52 -0700 "Scott Windsor" <[EMAIL PROTECTED]> wrote:
> Right now, my processes aren't gigantic... I'm preparing for a 'worst case' > scenario when I have a extremely large processes or memory usage. This can > easily happen on specific applications such as an image server (using image > magick) or parsing/creating large xml payloads (a large REST server). For > those applications, I may have a large amount of memory used for each > request, which will increase until the GC is run. Well, does that mean you DO have this problem or DO NOT have this problem? If you aren't actually facing a real problem that could be solved by this change then you most likely won't get very far. Any imagined scenario you come up with could easily just be avoided. If you want to do this then you'll have to write code and you'll have to learn how to make a Mongrel handler that is registered before and after the regular rails handler. All you do is have this before handler analyze the request and disable the GC on the way in. In the after handler you just have to renable the GC and make it do the work. It's pretty simple, but *you* will have to go read Mongrel code and understand it first. Otherwise you're just wasting your time really. -- Zed A. Shaw - Hate: http://savingtheinternetwithhate.com/ - Good: http://www.zedshaw.com/ - Evil: http://yearofevil.com/ _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
