From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 8769B3B29F for ; Sat, 22 Oct 2016 21:33:30 -0400 (EDT) Received: by mail-wm0-x236.google.com with SMTP id b80so46269072wme.1 for ; Sat, 22 Oct 2016 18:33:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:cc; bh=e0x8s9Li2n0pNpE6B3EIq0iNu5r5u0+L78BRWCwq4mA=; b=kWKJHRYI61APziIo2ZrDu35fva91HSCG96hc2B2YkudUurv/e4NLCEYwBPx86iulmq k9Irn8To/p681tuVy/MTqS9Fj1bBoU31ImxKnbALGv/ZL2s/Hkytdqt4K9cZ96c4/BkV EI/F7jNp8s8V4o2VZa7+V/H/y8udVwO7hQV9Kzvz/tIJiscRUqQFm7T0fD4pR2MeWvtq ARR4TKz5BmTZ/g/GKy+vm+yiH6ayDlBrPlyws7MXL9MI9Cdl3Kh67BqafOJ+K876lNUr Taz3sZWsi1ZCyBVJ7l68gcWqR35UAcPRO+mFGxz3K8McdhUMO7v2QDoR8L1rg8u/+WyL RC6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:cc; bh=e0x8s9Li2n0pNpE6B3EIq0iNu5r5u0+L78BRWCwq4mA=; b=hgccGCy74R6j09JJyteTkxe5m0hCNc5cdoeUKZpnLrQ4+y1vFkRO3zHcUCxT3N5qDX 0zLOFXcMjBmT4ejAno4REYpDTG42jXtb+ZbOC9XTsWWjbB5jUwkUFnnd3EJLuayMBbih 9znpHOYfeQ4kORBVnT3HVV6i4scmLhGSrpyDF6n7GhS/3t6lDIjrbkBAgDIHvT4LidFg OVgYqkLpzhCLyCRro0KIdi4esmtzUU0oisY3k77OJ5FXHXaTIwi551SC/YI6eTe22VF4 CWBpD7NPUHwibO0a1gr4HR7/ZbknC7e2JrNwPdZf/Nxf34sYYzIGtiIic8duwm0JfxcI pFCg== X-Gm-Message-State: ABUngve2VfOb16meyQAaQbW/13NESGo1uEnvU08K2gfIt+MG5EsIxp7RGOupNLvQ5n2GX44DBVPwZFZ5LoBp9w== X-Received: by 10.28.26.75 with SMTP id a72mr8528425wma.36.1477186409443; Sat, 22 Oct 2016 18:33:29 -0700 (PDT) MIME-Version: 1.0 Sender: justinbeech@gmail.com Received: by 10.28.207.134 with HTTP; Sat, 22 Oct 2016 18:33:28 -0700 (PDT) In-Reply-To: References: From: jb Date: Sun, 23 Oct 2016 12:33:28 +1100 X-Google-Sender-Auth: MZZ9UtFcI8CexoOwU6lFb0iky-w Message-ID: Cc: bloat Content-Type: multipart/alternative; boundary=001a114cd8be33b590053f7e4324 Subject: Re: [Bloat] 22 seconds til bloat on gfiber? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2016 01:33:30 -0000 --001a114cd8be33b590053f7e4324 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 bloa= t 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 wrote: > > > On 23 Oct, 2016, at 00:56, Dave Taht wrote: > > > > http://www.dslreports.com/speedtest/5408767 > > Looks like that=E2=80=99s how long it takes for the throughput to ramp up= to link > capacity. That in turn is a function of the sender=E2=80=99s TCP. > > - Jonathan Morton > > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat > --001a114cd8be33b590053f7e4324 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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 t= o full speed
because that is a function of =C2=A0the 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 sp= eed.

There is an upload duration preference that can inc= rease 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, O= ct 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=E2=80=99s how long it takes for the throughput to ramp up t= o link capacity.=C2=A0 That in turn is a function of the sender=E2=80=99s T= CP.

=C2=A0- Jonathan Morton

_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net<= /a>
https://lists.bufferbloat.net/listinfo/bloat

--001a114cd8be33b590053f7e4324--