Re: Maintaining capacity during deploys

[Tony Arcieri <tony.arcieri@gmail.com>]

Here's a quick followup with what we're going to try:

We changed the before_fork/after_fork hooks, getting rid of the
original before_fork hook which sent SIGQUIT to the old master.
Instead, we send SIGTTOU to the old master at the very end of the
after_fork block, so that as each new worker completes booting it
tells the old master to kill off one old worker.

We're also using Rack::MockRequest in the after_fork block (but before
we send SIGTTOU) to send a request to our most heavily trafficked
action. Subsequent requests to the same action are ~20X faster, so
it's clear we're pulling in a lot of code on that first request and
warming up the new workers is definitely needed.

Does this sound sane?

--
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