From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (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 3FD6C3B29F for ; Sat, 22 Oct 2016 21:47:15 -0400 (EDT) Received: by mail-qk0-x230.google.com with SMTP id z190so197071224qkc.2 for ; Sat, 22 Oct 2016 18:47:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=udZVclnbTbeERcG7wfW/+M4XGUhJAfaQYUyGx6pnE2Y=; b=Yeo6RIKo/zm+LpaonqjZfUFlMVybNplOsMmuchzC6qvJZY3NaNDFmRIjOlkHXb8X95 mOO5q0R4PkNMD5XoR1bSvXPDcEf5FgM8gHm+K3QdpDSKG7wHTDu6y2jVacR97fx8Kn0+ Nsx8z1NFfVyn/rtYMqjsGMphY+JD7GfdAvG1DaQBjFSAN7CNSn2apdkOspFXzxNyEwbO L201QjqFFm49XQx2zTFOhmeyTgA03IAmog/3gIYZ84Y5FDTXVqZZnBkM5Barr1VNf3Rc AsOIZ+6PBGZVhpTdGBwUWFPS7DgqKACKrUFqQdogKtKrOFqq0hoK70EAGVH//BnuLGMO KVTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=udZVclnbTbeERcG7wfW/+M4XGUhJAfaQYUyGx6pnE2Y=; b=dzQGKMrVWuh4sUyAceiD+99GT/Ap9cBsnpRGduNTI4zTwNow+9oFHaX8DVXvWbndTm JCMW4pd3ANJfXL7J2kxl1rHnOpp2/6OK8fn0B67+v3RH+9uVEMM0OubWuKFUjligbqI6 A5fkEcsJ4UC/7e7xGVboU8BUORozWTK4jVSwmi9riSutawPP0T2hwAEWlZwfVNKpf1Pz LthxPBMRvuEwmK6TOvVMvTPsiIVvexALIp/xJV9mdyL2OkGLIjyE6dfF7jSpQnzdBtD8 9ZWJio/AMoqEjH0Ta4wn8uc7QCPhZgc5zn/FqR+x4yyVHxXdBRUEh5i1pJTC6iVXoGIc Y1cw== X-Gm-Message-State: ABUngveiQxBXNrZ/b7QOH0vxWUGlWTBdby75Bm+Z7lfavobBeGnMSkY7g+bGhN7dGvLSscnLYv23lEDG8akRKg== X-Received: by 10.55.168.66 with SMTP id r63mr8638887qke.118.1477187234763; Sat, 22 Oct 2016 18:47:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.146.164 with HTTP; Sat, 22 Oct 2016 18:47:14 -0700 (PDT) In-Reply-To: References: From: Dave Taht Date: Sat, 22 Oct 2016 18:47:14 -0700 Message-ID: To: jb Cc: bloat Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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:47:15 -0000 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 wrote: > On Sat, Oct 22, 2016 at 6:33 PM, jb 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 b= loat >> 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 tes= t. > > 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 >> 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 >> >> >> >> _______________________________________________ >> Bloat mailing list >> Bloat@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/bloat >> > > > > -- > Dave T=C3=A4ht > Let's go make home routers and wifi faster! With better software! > http://blog.cerowrt.org --=20 Dave T=C3=A4ht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org