On Feb 6, 2008 12:46 AM, 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.
You're talking about mongrel, or mongrel_rails? The thing with that will be force garbage collection on every request will hit (and hard) the performance of the server. Also, is not Mongrel job if the framework behind it (in this case, Rails) generate so many objects that cross 8M limit set by VM (which usually trigger GC collection). There was a patch submitted a few days back to ruby-core about Benchmark.realtime that reduce memory allocation and increase performance. The problem was Rails use it extensively on every place and several times *per request*, eating memory and reducing performance... Just my comments :-) -- Luis Lavena Multimedia systems - A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. Douglas Adams _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
