We currently handle GC in a after_filter :cleanup for controllers that use a lot of ram *ahem* image magic.
Cheers Dave On 07/02/2008, at 5:02 PM, Zed A. Shaw wrote: > On Wed, 6 Feb 2008 03:46:34 +0100 > Roger Pack <[EMAIL PROTECTED]> wrote: > >> Would it make sense to add the option for mongrel to disable GC >> during a >> request and enable it after? Or even run it after? >> Just thinking out loud. >> Thanks for Mongrel. > > Not sure, it's probably not get you far since you'd end up paying for > it later anyway. I'd say try it for one or two actions or as a couple > of mongrel handlers and see if it helps you. You coudl also do it > filter style that would let you just do this GC hackery for one > request. > > -- > 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 _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
