From: Eric Wong <firstname.lastname@example.org>
To: unicorn list <email@example.com>
Subject: Re: listen backlog
Date: Fri, 3 Dec 2010 13:49:06 -0800 [thread overview]
Message-ID: <20101203214906.GA11366@dcvr.yhbt.net> (raw)
> On Thu, Dec 2, 2010 at 11:35 PM, Eric Wong <firstname.lastname@example.org> wrote:
> > UNIX sockets are faster for nginx <-> Unicorn, but Raindrops is slower
> > dealing with them since Linux doesn't export UNIX sockets stats to
> > netlink the same way it does for TCP sockets. So there's always a
> > tradeoff :x
> When does that netlink speed difference matter - only when collecting stats?
Yes, the performance difference is only when collecting stats.
> Using "modprobe inet_diag" made the script spit out a new error:
> address active queued
> linux-tcp-listener-stats.rb:42:in `tcp_listener_stats': NLMSG_ERROR
> from linux-tcp-listener-stats.rb:42
I don't think I've ever seen NLMSG_ERROR before. Are you running
this as the same user that originally bound the listener (the user
of the Unicorn master process)?
> $ sudo modprobe -l inet_diag
> I dug in to raindrops a little bit, and it seems the error associated
> with the NLMSG_ERROR is -2,
> "No such file or directory".
Are you bound to 0.0.0.0:9000 and not 127.0.0.1:9000? Use
0.0.0.0:9000 if you're bound to that (I had another user on the
raindrops mailing list with that problem).
Unicorn mailing list - email@example.com
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2010-12-03 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 1:35 listen backlog ghazel
2010-12-03 2:39 ` Eric Wong
2010-12-03 5:31 ` ghazel
2010-12-03 7:35 ` Eric Wong
2010-12-03 9:16 ` ghazel
2010-12-03 21:49 ` Eric Wong [this message]
2010-12-03 22:49 ` ghazel
2010-12-04 23:48 ` Eric Wong
2010-12-05 0:02 ` ghazel
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 \
* 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).