Evan Weaver wrote: > Disabling GC around the requests would guarantee that the size of the > Mongrel process will balloon to the size of all objects combined in > the most heavyweight request. Remember that the Ruby heap never > returns space to the OS. As soon as you re-enable the GC, the entire > Ruby heap (now 4-5x bigger than it normally would be) will get paged > back in to physical RAM. >
One thing that could be done is to force a GC every "x" requests--that way a GC is for sure run between requests [at least with single threaded rails] and that way the stack is most shallow and the GC will not pick up ghost references left on the stack. But hopefully we won't have to worry about that soon :) -=R -- Posted via http://www.ruby-forum.com/. _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
