From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Maintaining capacity during deploys
Date: Fri, 30 Nov 2012 01:24:47 +0000 [thread overview]
Message-ID: <20121130012447.GA10092@dcvr.yhbt.net> (raw)
In-Reply-To: <CAHOTMV+LNF3XhtMo8P9dmwfE4zsPiUNBCizHrtSVhL+Zeh6dJw@mail.gmail.com>
Tony Arcieri <tony.arcieri@gmail.com> wrote:
> On Thu, Nov 29, 2012 at 3:34 PM, Lawrence Pit <lawrence.pit@gmail.com> wrote:
> >
> > Perhaps it's possible to warm up the workers in the unicorn after_fork block?
>
> Are people doing this in production (i.e. moving the termination of
> the old master from before_fork to after_fork)? My worry is that
> during this warming process you will have 2X the normal number of
> Unicorn workers active at the same time, which could potentially lead
> to exhausting of system resources (i.e. RAM)
I haven't done any terminations in the *_fork hooks for a long time.
I just let 2x the normal workers run for a bit before sending SIGQUIT.
That said, I usually have plenty of RAM (and DB connections) to spare.
Excessive CPU-bound loads are handled very well nowadays.
_______________________________________________
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
next prev parent reply other threads:[~2012-11-30 1:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHOTMV++otgxdru_oZLXuVuqHF7F4uMwd04O0QZBjxeqFR-=XQ@mail.gmail.com>
2012-11-29 23:05 ` Fwd: Maintaining capacity during deploys Tony Arcieri
2012-11-29 23:09 ` Alex Sharp
2012-11-29 23:32 ` Fwd: " Eric Wong
2012-11-29 23:52 ` Tony Arcieri
2012-11-30 21:28 ` Tony Arcieri
2012-11-30 22:27 ` Eric Wong
2012-12-03 23:53 ` Tony Arcieri
2012-12-04 0:34 ` Eric Wong
2012-11-29 23:34 ` Lawrence Pit
2012-11-30 1:10 ` Tony Arcieri
2012-11-30 1:24 ` Eric Wong [this message]
2012-11-30 4:48 ` seth.cousins
2012-11-30 1:28 ` Devin Ben-Hur
2012-11-30 1:40 ` Tony Arcieri
2012-12-07 23:42 ` Tony Arcieri
2012-12-07 23:54 ` Eric Wong
2012-12-28 21:38 ` Dan Melnick
2012-12-28 22:07 ` Tony Arcieri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121130012447.GA10092@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).