Tony <[email protected]> wrote: > It seems like OobGC configuration is all predicated around a number of > requests to process before OobGCing. However, REE exposes heap/GC > stats that could be used to make that decision intelligently at > runtime.
We're having the exact same issues here. Also, I find using God to kill workers over memory limits as relatively awkward. It would be great if we could have a proc run after each request. It would be nice if we could check memory usage and then either run the GC or signal QUIT if too much memory has leaked (usually happens after around 10 minutes for us). Clifton _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
