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: listen backlog
Date: Thu, 2 Dec 2010 18:39:19 -0800	[thread overview]
Message-ID: <20101203023919.GA4411@dcvr.yhbt.net> (raw)
In-Reply-To: <AANLkTikJT29C36cBW6-evhAVVpJxbF09JiGo_b08aQGg@mail.gmail.com>

ghazel@gmail.com wrote:
> I found this thread
> http://rubyforge.org/pipermail/mongrel-unicorn/2009-September/000031.html
> after googling for the same error located in my nginx error log.
> 
> Is there some way to discover the current queue length of the backlog?
> Increasing the maximum size to 2048 "worked" for me as well, but
> obviously clients sit in the queue for a long time. If I could monitor
> queue length I could get some idea of when I have insufficient unicorn
> workers before the delay gets very high or requests fail.

If you're using Linux, you can use Raindrops[1] to interrogate
via inet_diag or parse /proc/net/{tcp,unix} yourself.

You can run Raindrops separate/standalone script:
http://git.bogomips.org/cgit/raindrops.git/tree/examples/linux-tcp-listener-stats.rb

Or use it as middleware (see webpage):
http://raindrops.bogomips.org/

git clone git://git.bogomips.org/raindrops

-- 
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-12-03  3:24 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 [this message]
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
2010-12-03 22:49           ` ghazel
2010-12-04 23:48             ` Eric Wong
2010-12-05  0:02               ` ghazel

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=20101203023919.GA4411@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).