unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: scaling unicorn
Date: Tue, 22 Jun 2010 04:53:46 +0000	[thread overview]
Message-ID: <20100622045346.GA23710@dcvr.yhbt.net> (raw)
In-Reply-To: <F596AC52-4CD1-4543-9B04-7A19762995DC@tramchase.com>

Jamie Wilkinson <jamie@tramchase.com> wrote:
> On Jun 21, 2010, at 5:16 PM, Eric Wong wrote:
> >> overloading the server or hitting memory bandwidth issues.  The
> >> backlog is at the somaxconn default of 128, I'm still not sure if
> >> we will bump that up or not.
> > 
> > The default backlog we try to specify is actually 1024 (same as
> > Mongrel).  But it's always a murky value anyways, as it's
> > kernel/sysctl-dependent.  With Unix domain sockets, some folks use
> > crazy values like 2048 to look better on synthetic benchmarks :)
>  
> Somewhat related -- I've been meaning to discuss the finer points of
> backlog tuning.
>  
> I've been experimenting with the multi-server socket+TCP megaunicorn
> configuration from your CDT:
> http://rubyforge.org/pipermail/mongrel-unicorn/2009-September/000033.html
> 
> Which I think is what this sentence from TUNING is talking about?
>  
> 	"Setting a very low value for the :backlog parameter in “listen”
> 	directives can allow failover to happen more quickly if your
> 	cluster is configured for it."

Yes.

<snip>

Thanks for sharing, and good to this is working well for you.

I'm still unlikely to have the chance to test this anywhere soon, but
maybe more folks can give it a try now that we've had one successful
report.   More reports (success or not) would definitely be good
to hear.

> BTW, this configuration needs a cool name!

Since you're the first person brave enough to try (or at least report
about it), you shall have the honor of naming it :)

-- 
Eric Wong
_______________________________________________
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

  reply	other threads:[~2010-06-22  4:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTilv4e_DPDKy440xotrlE7ucFIFXs74uHyGrzCKL@mail.gmail.com>
2010-06-22  0:16 ` [Mongrel] scaling unicorn Eric Wong
2010-06-22  2:34   ` Jamie Wilkinson
2010-06-22  4:53     ` Eric Wong [this message]
2010-06-22 18:03       ` snacktime
2010-06-22 18:57         ` Jamie Wilkinson
2010-06-23  9:32         ` Eric Wong
2010-06-22 19:18       ` Jamie Wilkinson
2010-06-22 17:30   ` [Mongrel] " snacktime

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=20100622045346.GA23710@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).