General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: jb <justin@dslr.net>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bloat goes away, but with ~25% speed loss?
Date: Sat, 6 Jun 2015 20:22:34 +1000	[thread overview]
Message-ID: <CAH3Ss97bk9YHfPXvYWK3qrA0c+MNUDovhC78NT6k=h1gMC6NUw@mail.gmail.com> (raw)
In-Reply-To: <5572C5AE.7040300@darbyshire-bryant.me.uk>

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

All input is good. Because the general web using population seems to have
barely enough focus to last the length a tweet compared to even five years
ago.

I do tend to react and type first, then later it does have the desired
impact so sorry if it came over as a bit defensive. I fully agree with your
caution in going for big ranking lists!

On Sat, Jun 6, 2015 at 8:04 PM, Kevin Darbyshire-Bryant <
kevin@darbyshire-bryant.me.uk> wrote:

>  On 06/06/2015 10:30, jb wrote:
>
> My 2c - I wasn't planning on creating pages listing ISPs in order of
> decreasing buffer bloat score.
>
> Good :-)
>
>
>  And for speeds of course in the USA and most markets there are ranges of
> products each with their own speed and price attached, so ranking ISPs by
> any simple averaging of speeds is pointless as well.
>
> Absolutely.  I despair in this country because there's a regular 'ISP A is
> faster than ISP B' graph/battle...and it really makes no sense.
>
>
>  However I think there is value in map-based speed results especially
> ones that pin down average speeds and technologies to streets and towns,
> and if there is any value at all in grading a single test for bufferbloat
> (or latency to major cities, or jitter, or packet loss ..) then there is
> also value in combining those statistics.
>
> If you're in a geographical/single supplier situation then yes.  In the UK
> it simply doesn't work like that, any area, 'any' supplier.
>
>
>  And even just pure speeds, one can statistically work out products and
> create interesting comparisons, both spot, and changes over time. Even if,
> at least in the US, there is no way to switch because your local cable
> company is your local cable company.
>
> Our speeds are fundamentally controlled by how close to the
> cabinet/exchange you are, not really ISP controlled.  There are 2 bandings
> on VDSL though, 80/20, 40/10.  ADSL is a bit more 'best effort'
> Incidentally VDSL is advertised as a 'fibre' service in this country!  You
> can get real fibre, but really it's Fibre(rare to the home), Cable(Virgin
> Media), VDSL(effectively BT), ADSL(BT&others)
>
>
>  There is also value in showing just how far a few ISPs are ahead of
> everyone.
>
>  For example, in the USA, any speed ranking would put google fiber far
> out in front, and Verizon FIOS far in front for upload speed. Why hide that
> information? There may be a few ISPs that really get on top of buffer bloat
> as well, and highlighting those, if they exist, makes sense to me. This can
> be done without doing a top 100 chart full of nonsense.
>
> :-)  No top 100 nonsense yay :-)
>
> I *am* very interested to see up/down bufferbloat split out by
> ISP/delivery technology though.  And I am very positive about the
> dslreports bloat test, it's really very good and it's great to see people
> making the issue of bufferbloat more measurable and more mainstream.
> Apologies if I've sounded less than appreciative.
>
> Kevin
>

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

  reply	other threads:[~2015-06-06 10:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 21:18 Rich Brown
2015-06-04 20:01 ` Jonathan Morton
2015-06-05 14:33   ` Kevin Darbyshire-Bryant
2015-06-05 16:19     ` Dave Taht
2015-06-05 17:20       ` Kevin Darbyshire-Bryant
2015-06-05 17:23         ` Dave Taht
2015-06-05 17:25           ` Adrian Kennard
2015-06-05 17:27           ` Adrian Kennard
2015-06-05 17:44             ` Kevin Darbyshire-Bryant
2015-06-05 17:48             ` Dave Taht
2015-06-05 17:51               ` Adrian Kennard
2015-06-05 17:57                 ` Kevin Darbyshire-Bryant
2015-06-05 17:59                   ` Adrian Kennard
2015-06-05 19:44                     ` Dave Taht
2015-06-05 20:06                       ` Dave Taht
2015-06-05 22:45                         ` jb
2015-06-05 22:52                           ` Dave Taht
     [not found]                           ` <55722786.7090904@hp.com>
2015-06-06  0:32                             ` jb
2015-06-06  0:40                               ` Rick Jones
2015-06-06  3:54                         ` Aaron Wood
2015-06-06  4:13                           ` jb
2015-06-06  8:45                         ` Kevin Darbyshire-Bryant
2015-06-06  9:30                           ` jb
2015-06-06 10:04                             ` Kevin Darbyshire-Bryant
2015-06-06 10:22                               ` jb [this message]
2015-06-04 23:32 ` Aaron Wood
2015-06-04 23:38 ` Rick Jones

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='CAH3Ss97bk9YHfPXvYWK3qrA0c+MNUDovhC78NT6k=h1gMC6NUw@mail.gmail.com' \
    --to=justin@dslr.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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