> Do you mean something like Delayed Job via rake via Upstart? Or would using the Rails (3.0) console affect the master process somehow?
I don't think so. Delayed job and rails console are independent processes. They won't affect unicorn master process. There are some gem libraries that work in thread. For example, NewRelic and AirBrake use thread to report errors and metrics without blocking your application. Probably you want to look at libraries like them. Tatsuya On 15 May 2013 10:57, Eric Wong <normalper...@yhbt.net> wrote: > > Andrew Stewart <b...@airbladesoftware.com> wrote: > > On Wed, May 15, 2013, at 11:28 AM, Eric Wong wrote: > > > If you're using preload_app, I suspect it's some background thread > > > or hook causing it. Otherwise, can you reproduce this with a barebones > > > application? > > > > Do you mean something like Delayed Job via rake via Upstart? Or would > > using the Rails (3.0) console affect the master process somehow? > > Do any of those connect to the master? Hopefully somebody else here > knows more about Delayed Job and Rails more than I do. > > Also, if you have something constantly sending signals to the master in > a loop, unicorn (and maybe Ruby itself) may have trouble from queueing > signals up. > _______________________________________________ > 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 _______________________________________________ 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
