From: jb <justin@dslr.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] 22 seconds til bloat on gfiber?
Date: Sun, 23 Oct 2016 12:33:28 +1100 [thread overview]
Message-ID: <CAH3Ss96n=-KghwZBAsdrY7kGNSkoW+aDKfeqhwS7p2MMjh-cwg@mail.gmail.com> (raw)
In-Reply-To: <B1527C60-DCAE-40A1-985D-14DBFCCBCD5E@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
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.
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
>
[-- Attachment #2: Type: text/html, Size: 2077 bytes --]
next prev parent reply other threads:[~2016-10-23 1:33 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 [this message]
2016-10-23 1:45 ` Dave Taht
2016-10-23 1:47 ` Dave Taht
2016-10-23 2:27 ` jb
[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='CAH3Ss96n=-KghwZBAsdrY7kGNSkoW+aDKfeqhwS7p2MMjh-cwg@mail.gmail.com' \
--to=justin@dslr.net \
--cc=bloat@lists.bufferbloat.net \
/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