raindrops RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: John Pignata <john@pignata.com>
To: raindrops@librelist.org
Subject: Fwd: Queued vs. Active in tcp_stats_listener
Date: Sun, 3 Mar 2013 16:09:23 -0500	[thread overview]
Message-ID: <CAHzRVjPo99FD8Hby9ws=Tv56CvA_gZw-BMkn+zmxF2Gc1+nNSw@mail.gmail.com> (raw)
In-Reply-To: CAHzRVjNOLb+UeNx4EGrUPbjdLkpku0Ppkbo4VU8c1260N-QhiA@mail.gmail.com

Hi all,

I'm attempting to use Raindrops in order to start instrumenting our Unicorn
workloads on Heroku using statsd. I'm a little confused at the numbers it
reports under test.

My primary confusion is that our active number never climbs above the
number of workers we have running. Since we have a large backlog, I
expected to see the total number of accept()'ed clients counted in this
number too. Unfortunately, I only spikes up to the total number of workers
and queued never spikes above 0. I expected the latter as we shouldn't ever
be refusing connections with our large backlog.

If active represents the number of requests that are currently being
serviced and queued represents the number of connections that have yet to
be accept()'ed, is there a way to get out the middle state: requests that
have been accept()'ed but not yet started?


       reply	other threads:[~2013-03-03 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHzRVjNOLb+UeNx4EGrUPbjdLkpku0Ppkbo4VU8c1260N-QhiA@mail.gmail.com>
2013-03-03 21:09 ` John Pignata [this message]
2013-03-03 21:46   ` Fwd: Queued vs. Active in tcp_stats_listener Eric Wong
2013-03-03 22:26     ` John Pignata

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: http://yhbt.net/raindrops/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHzRVjPo99FD8Hby9ws=Tv56CvA_gZw-BMkn+zmxF2Gc1+nNSw@mail.gmail.com' \
    --to=john@pignata.com \
    --cc=raindrops@librelist.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).