From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] better business bufferbloat monitoring tools?
Date: Tue, 12 May 2015 15:17:34 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1505121515130.644@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw4EEcrXOQ7SA9tbFyXaLeR5ReSQUG6VGQWg3Us-2_kD-Q@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2679 bytes --]
On Tue, 12 May 2015, Dave Taht wrote:
> One thread bothering me on dslreports.com is that some folk seem to
> think you only get bufferbloat if you stress test the network, where
> transient bufferbloat is happening all the time, everywhere.
>
> On one of my main sqm'd network gateways, day in, day out, it reports
> about 6000 drops or ecn marks on ingress, and about 300 on egress.
> Before I doubled the bandwidth that main box got, the drop rate used
> to be much higher, and a great deal of the bloat, drops, etc, has now
> moved into the wifi APs deeper into the network where I am not
> monitoring it effectively.
>
> I would love to see tools like mrtg, cacti, nagios and smokeping[1] be
> more closely integrated, with bloat related plugins, and in
> particular, as things like fq_codel and other ecn enabled aqms deploy,
> start also tracking congestive events like loss and ecn CE markings on
> the bandwidth tracking graphs.
>
> This would counteract to some extent the classic 5 minute bandwidth
> summaries everyone looks at, that hide real traffic bursts, latencies
> and loss at sub 5 minute timescales.
The problem is that too many people don't realize that network utilization is
never 50%, it's always 0% or 100% (if you look at a small enough timeslice).
With a 5 min ave, 20% utilization could be 100% maxed out and buffering for 60
seconds, and then idle for the remainder of the time.
I always set my graphs for 1 min samples (and am very tempted to go shorter)
just because 5 min hides so much.
David Lang
> mrtg and cacti rely on snmp. While loss statistics are deeply part of
> snmp, I am not aware of there being a mib for CE events and a quick
> google search was unrevealing. ?
>
> There is also a need for more cross-network monitoring using tools
> such as that done by this excellent paper.
>
> http://www.caida.org/publications/papers/2014/measurement_analysis_internet_interconnection/measurement_analysis_internet_interconnection.pdf
>
> [1] the network monitoring tools market is quite vast and has many
> commercial applications, like intermapper, forks of nagios, vendor
> specific producs from cisco, etc, etc. Far too many to list, and so
> far as I know, none are reporting ECN related stats, nor combining
> latency and loss with bandwidth graphs. I would love to know if any
> products, commercial or open source, did....
>
> --
> Dave Täht
> Open Networking needs **Open Source Hardware**
>
> https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2015-05-12 22:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 16:00 Dave Taht
2015-05-12 22:17 ` David Lang [this message]
2015-05-13 13:20 ` [Cerowrt-devel] [Bloat] " Bill Ver Steeg (versteb)
2015-05-13 13:36 ` Dave Taht
2015-05-13 17:51 ` Bill Ver Steeg (versteb)
2015-05-14 15:40 ` [Cerowrt-devel] RE : " luca.muscariello
2015-05-13 15:30 ` [Cerowrt-devel] " Jim Gettys
2015-05-14 14:28 ` dpreed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1505121515130.644@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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