General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: jb <justin@dslr.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] 22 seconds til bloat on gfiber?
Date: Sun, 23 Oct 2016 13:27:00 +1100	[thread overview]
Message-ID: <CAH3Ss97zow3FWeq2hdFUVngkEBnUJ9F6s8q6-RAARdD51+Ut4A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6qQhkTU_qHTu0yaN447sjaNEpu_p2TWe3Zjg2DhgAhkg@mail.gmail.com>

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

Bloat starts here half way through upload, but it isn't nearly as bad as
the original example:
  https://www.dslreports.com/speedtest/5409732

I wonder if there is a browser or PC component to bad results on google
fiber I imagine they all have the same equipment?


On Sun, Oct 23, 2016 at 12:47 PM, Dave Taht <dave.taht@gmail.com> wrote:

> randomly clicking around, 18 seconds to "start of bloat" on xfinity
> http://www.dslreports.com/speedtest/5414347
>
> On Sat, Oct 22, 2016 at 6:45 PM, Dave Taht <dave.taht@gmail.com> wrote:
> > On Sat, Oct 22, 2016 at 6:33 PM, jb <justin@dslr.net> wrote:
> >> This example takes about 6 seconds to get all the uploads running as
> >> they are staged, and then each upload takes a while to get to full speed
> >> because that is a function of  the senders TCP stack. So the smoothed
> >> total transfer rate lags as well, and the whole thing doesn't start to
> bloat
> >> out until we get to max speed.
> >>
> >> There is an upload duration preference that can increase the total time
> >> upload or download takes but people already have no patience and
> >> close the tab when they start seeing decent upload numbers,
> >> so increasing it just makes the quit rate higher still. For the quitters
> >> we get no results at all, other than they quit before the end of the
> test.
> >
> > I agree that waiting that long is hard on users, and that since it
> > takes so long to get to that point, it will take a lot of work for a
> > gfiber user to stress out the connection, on a benchmark... but in the
> > real world, with a few users on the link, not so much.
> >
> > 400-1000ms latency when loaded counts as an "F" grade, in my opinion.
> > Perhaps doing the grade calculation only when the link is observed
> > near max bandwidth achieved (say, half)?
> >
> > There are of course, other possible reasons for such bloat, like the
> > browser falling over, I wish I had a gfiber network and routing device
> > to test against.
> >
> > Is there any way to browse
> > http://www.dslreports.com/speedtest/results/isp/r3910-google-fiber for
> > like the last 20 results to see if this is a common behavior on gfiber
> > for longer tests?
> >
> >> thanks
> >>
> >> On Sun, Oct 23, 2016 at 10:52 AM, Jonathan Morton <
> chromatix99@gmail.com>
> >> wrote:
> >>>
> >>>
> >>> > On 23 Oct, 2016, at 00:56, Dave Taht <dave.taht@gmail.com> wrote:
> >>> >
> >>> > http://www.dslreports.com/speedtest/5408767
> >>>
> >>> Looks like that’s how long it takes for the throughput to ramp up to
> link
> >>> capacity.  That in turn is a function of the sender’s TCP.
> >>>
> >>>  - Jonathan Morton
> >>>
> >>> _______________________________________________
> >>> Bloat mailing list
> >>> Bloat@lists.bufferbloat.net
> >>> https://lists.bufferbloat.net/listinfo/bloat
> >>
> >>
> >>
> >> _______________________________________________
> >> Bloat mailing list
> >> Bloat@lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/bloat
> >>
> >
> >
> >
> > --
> > Dave Täht
> > Let's go make home routers and wifi faster! With better software!
> > http://blog.cerowrt.org
>
>
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
>

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

  reply	other threads:[~2016-10-23  2:27 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22 21:56 Dave Taht
2016-10-22 23:52 ` Jonathan Morton
2016-10-23  1:33   ` jb
2016-10-23  1:45     ` Dave Taht
2016-10-23  1:47       ` Dave Taht
2016-10-23  2:27         ` jb [this message]
     [not found]           ` <CAJq5cE3DsV9v6ATVeq+vF_kVFjKy+8Qjwe-P01ZZbyKZB9HC6w@mail.gmail.com>
2016-10-23  8:29             ` Jonathan Morton
2016-10-23  9:23               ` jb
2016-10-23 16:14                 ` Klatsky, Carl
2016-10-24  0:46                   ` jb
2016-10-24 13:13                     ` Klatsky, Carl
2016-10-24 16:11                       ` Noah Causin
2016-10-24 20:27                         ` Klatsky, Carl
2016-10-23  2:30         ` Benjamin Cronce
2016-10-25  7:10   ` Jonas Mårtensson
2016-10-23  5:50 ` Mikael Abrahamsson
2016-10-24 16:57   ` Jonas Mårtensson
2016-10-24 22:10     ` Benjamin Cronce
2016-10-25  0:09       ` jb
2016-10-25 12:01         ` Benjamin Cronce
2016-10-25 13:11         ` Klatsky, Carl
2016-10-25 21:20           ` jb
2016-10-26  0:02             ` Klatsky, Carl
2016-10-25 15:59       ` Jan Ceuleers
2016-10-26  1:05         ` Benjamin Cronce
2016-10-26 14:49           ` Jan Ceuleers
2016-10-26 15:36             ` Mikael Abrahamsson
2016-10-27 14:32               ` Jonas Mårtensson
2016-10-27 16:56                 ` Dave Taht
2016-10-27 17:56                   ` [Bloat] Sidebar on s-curves David Collier-Brown
2016-10-27 19:30                   ` [Bloat] 22 seconds til bloat on gfiber? David Lang
2016-10-27 19:41                     ` Dave Taht
2016-10-27 19:48                       ` Aaron Wood
2016-10-28 15:51                         ` Jan Ceuleers
2016-10-28 15:55                           ` Klatsky, Carl
2016-10-27 19:45                     ` Aaron Wood
2016-10-27 20:17                   ` Mikael Abrahamsson
2016-12-07  5:40                     ` Jonathan Morton
2016-12-07  7:05                       ` Mikael Abrahamsson
     [not found] <mailman.313.1477591111.3555.bloat@lists.bufferbloat.net>
2016-10-27 19:27 ` Jonathan Foulkes

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=CAH3Ss97zow3FWeq2hdFUVngkEBnUJ9F6s8q6-RAARdD51+Ut4A@mail.gmail.com \
    --to=justin@dslr.net \
    --cc=bloat@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