General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: bloat@lists.bufferbloat.net,
	Kenneth Porter <shiva@sewingwitch.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] this explains speedtest stuff
Date: Sat, 25 Apr 2020 18:22:22 +0200	[thread overview]
Message-ID: <ECEF1F88-0CC6-45E6-B380-1FDEE55A827F@gmx.de> (raw)
In-Reply-To: <72d4d4a4-ad29-cdd8-0bf5-2413c7c845de@sewingwitch.com>

[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]

Hi Ken,

I tried to summarize a few recommendations under https://forum.openwrt.org/t/sqm-qos-recommended-settings-for-the-dslreports-speedtest-bufferbloat-testing/2803 maybe that is of some help...

Good luck
        Sebastian

On 25 April 2020 17:59:47 CEST, Kenneth Porter <shiva@sewingwitch.com> wrote:
>On 4/25/2020 8:43 AM, Dave Taht wrote:
>> and the last flaw of this test series is that ken took the dslreports
>> "fiber" setting for the dslreports test as "The right thing". the
>> "fiber" test is structured to stress test an asymmetric 1gbit/100mbit
>> connection, not a shaped fiber connection running at 50mbit
>symmetric.
>> The number of uploads is 4, downloads, 32.... it's totally ok to pick
>> a given fiber/cable/whatever test, but it does help to apply the same
>> characteristics to more of the tests you do, if you are trying to
>> compare technologies.
>
>I'd be happy to test with a different set of speed test settings. Would
>
>Corporate/Edu be a better choice?
>
>In going through this exercise, I can imagine someone saying "where'd 
>all the bandwidth I paid for go?" as we trade bandwidth for reduced 
>latency. How do you sell that to end users? ISPs have trained people to
>
>think only in terms of raw speed (obviously that's best for an ISP's 
>bottom line as they can upsell you the higher-priced package) and most 
>people (outside of gamers) don't really grasp latency with the 
>intuitiveness of speed. Maybe we need some Youtube videos showing end 
>user experiences of the benefit of reduced latency.
>
>
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 2326 bytes --]

  parent reply	other threads:[~2020-04-25 16:22 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 19:38 Dave Taht
2020-04-23 20:00 ` Jonathan Foulkes
2020-04-23 20:15   ` Sergey Fedorov
2020-04-23 20:27     ` Dave Taht
2020-04-24  1:03       ` Sergey Fedorov
2020-04-24  0:44 ` Kenneth Porter
2020-04-24  0:47   ` Jonathan Morton
2020-04-24  1:16     ` Kenneth Porter
     [not found]     ` <6F1F3C646A7DFD2CC8C9E79E@172.27.17.193>
2020-04-24  1:20       ` Dave Taht
2020-04-24  5:15         ` Matt Taggart
2020-04-24 14:40         ` Kenneth Porter
2020-04-24 14:52           ` Sebastian Moeller
2020-04-24 14:56           ` Toke Høiland-Jørgensen
     [not found]           ` <mailman.56.1587740202.24343.bloat@lists.bufferbloat.net>
2020-04-24 15:22             ` Kenneth Porter
2020-04-24 16:22         ` Kenneth Porter
2020-04-24 18:43           ` Jonathan Morton
2020-04-25  1:16             ` Kenneth Porter
2020-04-25  8:43               ` Jonathan Morton
2020-04-25 13:49                 ` Kenneth Porter
2020-04-25 14:00                   ` Jonathan Morton
2020-04-25 14:14                     ` Kenneth Porter
2020-04-25 14:19                       ` Jonathan Morton
2020-04-25 15:31                         ` Kenneth Porter
2020-04-25 15:33                           ` Dave Taht
2020-04-25 15:32                         ` Dave Taht
2020-04-25 15:43                           ` Dave Taht
2020-04-25 15:59                             ` Kenneth Porter
2020-04-25 16:06                               ` Dave Taht
2020-04-25 16:22                               ` Sebastian Moeller [this message]
2020-04-26 10:59                               ` Toke Høiland-Jørgensen
2020-04-25 15:52                           ` Kenneth Porter
2020-04-25 15:55                             ` Dave Taht
2020-04-25 16:18                               ` Kenneth Porter
2020-04-25 15:38                         ` Kenneth Porter
2020-04-25 17:22                     ` Y
     [not found]                     ` <mailman.73.1587835496.24343.bloat@lists.bufferbloat.net>
2020-04-25 17:37                       ` Jonathan Morton
2020-04-25 18:19                         ` Dave Taht
2020-04-25 20:49                           ` Kenneth Porter
     [not found]                           ` <787FB38B9372372F376BB072@172.27.17.193>
2020-04-25 20:55                             ` Dave Taht
     [not found]                 ` <3D2F4A70BAB1774D1EFDC641@172.27.17.193>
2020-04-25 16:00                   ` Dave Taht
2020-04-25 16:17                     ` Kenneth Porter
2020-04-26 10:51                       ` Toke Høiland-Jørgensen
2020-04-24 16:25         ` Kenneth Porter
     [not found]         ` <42D98FE80B7B9C1102C47579@172.27.17.193>
2020-04-24 16:32           ` Dave Taht
2020-04-24 16:39             ` Dave Taht
2020-04-24 17:42             ` Kenneth Porter

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=ECEF1F88-0CC6-45E6-B380-1FDEE55A827F@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=shiva@sewingwitch.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