On Thu, Nov 29, 2012 at 5:28 PM, Devin Ben-Hur <dben...@whitepages.com> wrote: > A better solution is to use a profiler to identify what extra work is being > done when an unwarm worker gets its first request and move that work into an > initialization step which occurs before fork when run with app preload > enabled.
I've done that, unfortunately that work is connection setup which must happen after forking or otherwise file descriptors would wind up shared between processes. -- Tony Arcieri _______________________________________________ Unicorn mailing list - mongrel-unicorn@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
