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: Hello excellent friends
Date: Mon, 30 Aug 2010 23:17:08 -0700	[thread overview]
Message-ID: <20100831061708.GA26170@dcvr.yhbt.net> (raw)
In-Reply-To: <2D00600E-51CB-49E4-ACD0-238FE9DB783A@gmail.com>

Curtis <curtis.schofield@gmail.com> wrote:
> I have read your tun in article and I have tried to make sysctl
> changes - the benchmarks are not very significant. I love how well the
> signals are laid out and how excellently unicorn responds to them - I
> am hoping to get back to mongrel like performance . We were using
> nginx to haproxy to 32 mongrels
> No I have set up a unix domain socket with 2mb send and receive buffer
> and a backlog of 2048 - I didn't see a change with the send receive
> buffer tuning and I have yet to try a smaller backlog to see. If that
> helps. Any info?

Hi, I'm not sure what size of requests and responses you get, but 2mb
seems like a lot, especially for requests (unless you handle a lot of
big uploads).

Even with large requests/responses, huge buffers means more pressure on
the kernel allocator and you're also hurting CPU cache locality.  So
larger buffers can hurt performance as well as help, I'll make a note of
that in the documentation.

The backlog shouldn't change performance much.  A larger one can let you
withstand short traffic bursts and increase reliability while

> I am tuning for osx in dev and centos5 in production. Thank you for
> your great work cleaning mongrel into a first class unix friend.

You're welcome!

Eric Wong
Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

      reply	other threads:[~2010-08-31  6:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31  3:57 Hello excellent friends Curtis
2010-08-31  6:17 ` Eric Wong [this message]

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:

  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=20100831061708.GA26170@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=mongrel-unicorn@rubyforge.org \


* 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


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