From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com
[IPv6:2607:f8b0:4864:20::736])
(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 662423B29D
for ; Thu, 19 Dec 2019 18:02:43 -0500 (EST)
Received: by mail-qk1-x736.google.com with SMTP id x129so6076331qke.8
for ; Thu, 19 Dec 2019 15:02:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=from:reply-to:subject:to:references:message-id:date:user-agent
:mime-version:in-reply-to:content-language;
bh=9wy3CRXVoEJPvaFxgncIKpcwmB4ZNORQwvdExHSU9J8=;
b=uvB1nIN48mUZcCnlLdDvL6R62Kuho9dr2ekd33xQq8TMFY/k3r8+hM82tVMhcf1jHD
8EX84COxthKB5LwH9A+/bP6DPDUv3tyc7+k2OY+mEHI82CC8gvjMxSsQEMjadRCdfz3B
qDfsYxqKmk2ORT4wYNx4sUxwXy/MgLrYW18C+I3aEgISomTlZX9DBE2P3FzSoXcZZPPo
A/ERsUsI8y5HtvlmhwAXAlOes698ny/q8KB/VT5aUqVmETTWJysLQbQSHPM4b+oyvqwq
3CPCapLQYeil3/PDcJ7qTjgQxZvMLAC93oyKqQtn8wAvAtcm0fKC17LEnUsp3NFrDjCq
+Ayw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:from:reply-to:subject:to:references:message-id
:date:user-agent:mime-version:in-reply-to:content-language;
bh=9wy3CRXVoEJPvaFxgncIKpcwmB4ZNORQwvdExHSU9J8=;
b=XlXo1eqFvEI0vxyDt1DkQEBNEyiabOG6ekV4mSKQnKHVbOQVEn4awuhOrNK4x1xi+9
rOHxKLH/8CL4/UHepV4Jvox2dmjvFUw5B01URlUfARCK2uP1dDsmtTL/ilsHC1ybD5fV
qQNBSgRBqc5yQTVCPswzoyVN+ASMReBgXOUnL9vXJmw5DeI78fbM7mKSnKdtm8MhfSs+
AUbiQxartFcOAth7cSqJZb1g1Vqz4kII6/Oy0HAsezqUmvzY/Wcuy9t930d8O8rp7p7M
nFfz18DbPxH6wZnwmotmA+ikmqqDTbpsVdDQ/VYrCP2fKVHP5hqeKQD5pnIc8u0vbRMg
iNIw==
X-Gm-Message-State: APjAAAVk8xlYZ3Xx8L4gnwJK/PQ9N2twIsFgLdr1YzZwQE0e+r8pLF9a
6K6pvQHjuH6c950hBR2t09z/ItX/pzU=
X-Google-Smtp-Source: APXvYqzZHTBUp/qgapIEKv/JFRsztckNu7SVYTCbTiNSBgwszo/WW7e6Tumo4bFeWL1Yt/AS7grwSA==
X-Received: by 2002:a05:620a:a0b:: with SMTP id
i11mr10810861qka.11.1576796562954;
Thu, 19 Dec 2019 15:02:42 -0800 (PST)
Received: from ?IPv6:2607:fea8:5620:1699::7? ([2607:fea8:5620:1699::7])
by smtp.gmail.com with ESMTPSA id o7sm2186811qkd.119.2019.12.19.15.02.42
(version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
Thu, 19 Dec 2019 15:02:42 -0800 (PST)
From: David Collier-Brown
X-Google-Original-From: David Collier-Brown
Reply-To: davecb@spamcop.net
To: bloat@lists.bufferbloat.net
References:
Message-ID: <0151ae7d-6416-cf90-f13a-72dc26895d56@rogers.com>
Date: Thu, 19 Dec 2019 18:02:41 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Thunderbird/68.1.1
MIME-Version: 1.0
In-Reply-To:
Content-Type: multipart/alternative;
boundary="------------8D34EF37D2188DF47F7F2F43"
Content-Language: en-US
Subject: Re: [Bloat] some benchmarks from arstechnica
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: Thu, 19 Dec 2019 23:02:43 -0000
This is a multi-part message in MIME format.
--------------8D34EF37D2188DF47F7F2F43
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
I think he understands that he's talking about page fetch time to an
audience that won't believe that latency is like "latent fingerprints":
stuff that hasn't shown (up) yet.
Such folks annoy me (;-))
Note his quote usage in this:
> *IMPORTANT NOTE*about the -c {concurrency} option: if you ask for -c
> 10, each "page" will consist of 10 parallel fetches of URL, and the
> "latency" will be the amount of time it takes to get the last bit from
> the last concurrent child fetch.
--dave
On 2019-12-19 2:32 p.m., Dave Taht wrote:
> I was not aware that jim salter had really gone to town on measuring
> latency under load in the past year - notably the 4 stream 1024p + web
> browsing torture test used here:
>
> https://arstechnica.com/gadgets/2019/11/ars-puts-googles-new-nest-wi-fi-to-the-test/?itm_source=parsely-api
> https://arstechnica.com/gadgets/2019/12/amazons-inexpensive-eero-mesh-wi-fi-kit-is-shockingly-good/?comments=1
>
> He considers under 500ms of browsing latency to be "good". Not
> entirely sure how he's calculating that, I think he's measuring page
> completion time rather than "latency" per se'.
>
> The tools he uses are here:
>
> https://github.com/jimsalterjrs/network-testing/blob/master/README.md
>
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
--------------8D34EF37D2188DF47F7F2F43
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
I think he understands that he's talking about page fetch time to
an audience that won't believe that latency is like "latent
fingerprints": stuff that hasn't shown (up) yet.
Such folks annoy me (;-))
Note his quote usage in this:
IMPORTANT NOTE about the -c {concurrency} option:
if you ask for -c 10, each "page" will consist of 10 parallel
fetches of URL, and the "latency" will be the amount of time
it takes to get the last bit from the last concurrent child
fetch.
--dave
On 2019-12-19 2:32 p.m., Dave Taht
wrote:
I was not aware that jim salter had really gone to town on measuring
latency under load in the past year - notably the 4 stream 1024p + web
browsing torture test used here:
https://arstechnica.com/gadgets/2019/11/ars-puts-googles-new-nest-wi-fi-to-the-test/?itm_source=parsely-api
https://arstechnica.com/gadgets/2019/12/amazons-inexpensive-eero-mesh-wi-fi-kit-is-shockingly-good/?comments=1
He considers under 500ms of browsing latency to be "good". Not
entirely sure how he's calculating that, I think he's measuring page
completion time rather than "latency" per se'.
The tools he uses are here:
https://github.com/jimsalterjrs/network-testing/blob/master/README.md
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
--------------8D34EF37D2188DF47F7F2F43--