Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: "aqm@ietf.org" <aqm@ietf.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] ping loss "considered harmful"
Date: Sun, 1 Mar 2015 20:06:46 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1503012004060.26262@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw7KW=9PH002d3Via5ks6+mHScz5VDhpPVqLUGK2K=Mhew@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2503 bytes --]

On Sun, 1 Mar 2015, Dave Taht wrote:

> On this thread over here, an otherwise pretty clueful user chose
> openwrt's qos-scripts over the sqm-scripts, because sqm-scripts had
> *higher ping loss*.
>
>
> http://forums.dlink.com/index.php?topic=61634.msg251125#msg251125
>
> (I note that both fq_codel enabled QoS systems outperformed
> streamboost by a lot, which I am happy about)
>
> wow. It never registered to me that users might make a value judgement
> based on the amount of ping loss, and in looking back in time, I can
> think of multiple people that have said things based on their
> perception that losing pings was bad, and that sqm-scripts was "worse
> than something else because of it."

People make the assumption that if ping packets are being dropped, their data is 
getting dropped as well. This is part of the "dropped packets are bad, so buffer 
so you don't drop packets" mentality

To address this, the test results should first show all the stats without 
showing dropped packets, or if you need to show them, add a comment at that 
point that says that data packets are given priority over ping packets, so 
dropped ping packets don't imply that data packets would be dropped.

David Lang


> sqm-scripts explicitly *deprioritizes* ping. In particular, this
> reduces the impact of ping floods from ipv6 to your entire /64, or to
> your whole ipv4, fairly well. And I had made the point that
> prioritizing ping was a bad idea here (including some dripping sarcasm
> later in the piece).
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/Wondershaper_Must_Die
>
> but wow, it never occurred to me - in all these years - that ping was
> the next core metric on simple tests. I can be really dumb.
>
> I use netperf-wrapper and tend to ignore most of the ping data, but
> certainly on some benchmarks we have published ping doesn't look as
> good as the other stuff, *because it is deprioritized below all the
> other traffic*. Not strictly rate limited - as some systems do by
> default, including openwrt, which is impossible to get right - just
> deprioritized....
>
> How can we fix this user perception, short of re-prioritizing ping in
> sqm-scripts?
>
> -- 
> Dave Täht
> Let's make wifi fast, less jittery and reliable again!
>
> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel

  parent reply	other threads:[~2015-03-02  4:06 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02  3:57 Dave Taht
2015-03-02  4:00 ` [Cerowrt-devel] [aqm] " Andrew Mcgregor
2015-03-02  4:05 ` Mikael Abrahamsson
2015-03-02  4:06 ` David Lang [this message]
2015-03-02  9:40 ` Brian Trammell
2015-03-02 10:17   ` Mikael Abrahamsson
2015-03-02 10:54     ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2015-03-02 12:44       ` dpreed
2015-03-02 14:45       ` Brian Trammell
2015-03-02 18:41         ` David Lang
2015-03-03  6:45     ` [Cerowrt-devel] " Valdis.Kletnieks
2015-03-04  8:14       ` Mikael Abrahamsson
2015-03-02 21:53   ` Joe Touch
2015-03-02 23:14     ` David Lang
2015-03-02 23:25       ` Joe Touch
2015-03-02 23:34         ` David Lang
2015-03-03  0:07           ` Andrew Mcgregor
2015-03-02 10:47 ` Dave Dolson
2015-03-02 10:49   ` Andrew Mcgregor
2015-03-02 18:36     ` David Lang
     [not found] ` <md2fsa$o1s$1@ger.gmane.org>
2015-03-02 20:33   ` Dave Dolson
2015-03-02 20:39     ` David Lang
2015-03-02 20:38   ` Dave Taht
2015-03-04  8:12     ` Mikael Abrahamsson
2015-03-03 17:20 ` Fred Baker (fred)
2015-03-03 17:29   ` [Cerowrt-devel] [Bloat] " Wesley Eddy
2015-03-03 18:00     ` [Cerowrt-devel] [aqm] [Bloat] " Fred Baker (fred)
2015-03-04  5:24       ` Dave Taht
2015-03-05 18:56         ` Curtis Villamizar
2015-03-05 19:50           ` [Cerowrt-devel] [Bloat] [aqm] " Rich Brown
2015-03-04 17:34       ` [Cerowrt-devel] [aqm] [Bloat] " dpreed
2015-03-04 19:45         ` Mikael Abrahamsson
2015-03-05 20:38 ` [Cerowrt-devel] " Matt Taggart
2015-03-05 20:53   ` Dave Taht

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.1503012004060.26262@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=aqm@ietf.org \
    --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