On Tue, Apr 22, 2014 at 6:21 PM, Sam Saffron <[email protected]> wrote: > I am spawning sidekiqs from the master process so I share memory > better, added this patch > > https://github.com/discourse/discourse/commit/4aaedb82d09d53159a99c3c94c0232c3cf5b0725 > > Thing is I need to be in the master thread for both checks and > spawning cause of this https://bugs.ruby-lang.org/issues/9751 > > Is there a cleaner way to hook in?
>From an operational perspective this seems like a significant premature optimization. I'd think twice before doing it. IME you really don't want asynchronous job handling in the same process space as a synchronous preforking webserver. Best to keep your concerns separated. And RAM is cheap. --Michael _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
