General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: dave.collier-brown@indexexchange.com
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] What's a good non-intrusive way to look at bloat (and perhaps things like gout (:-))
Date: Thu, 4 Jun 2020 01:30:01 +0300	[thread overview]
Message-ID: <B55EE88E-4AA5-4306-A3E1-0AC0F2B67AD6@gmail.com> (raw)
In-Reply-To: <c8d8ed64-f6d1-31c7-2749-6c0f3bc4c33f@indexexchange.com>

> On 4 Jun, 2020, at 1:21 am, Dave Collier-Brown <dave.collier-brown@indexexchange.com> wrote:
> 
> We've good tools to measure network performance under stress, by the simple expedient of stressing it, but is there a good approach I could recommend to my company to monitor a bunch of reasonably modern links,  without the measurement significantly affecting their state?
> 
> I don't mind increasing bandwidth usage, but I'm downright grumpy about adding to the service time: I have a transaction that times out for gross slowness if it takes much more that an tenth of a second, and it involves a scatter-gather interaction with at least 10 customers in that time.
> 
> I'm topically interested in bloat, but really we should understand "everything" about our links. If they can get the bloats like cattle, they can probably get the gout, like King Henry the Eighth (;-))
> 
> My platform is Centos 8, and I have lots of Smarter Colleagues to help.

My first advice would be to browse pollere.net for tools - like pping (passive ping), which monitors the latency of flows in transit.  That should give you some interesting information without adding any load at all.  There is also connmon (https://github.com/pollere/connmon).

 - Jonathan Morton

  reply	other threads:[~2020-06-03 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 22:21 Dave Collier-Brown
2020-06-03 22:30 ` Jonathan Morton [this message]
2020-06-04 10:56   ` Toke Høiland-Jørgensen
2020-06-04 12:25     ` Dave Collier-Brown

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://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=B55EE88E-4AA5-4306-A3E1-0AC0F2B67AD6@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.collier-brown@indexexchange.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox