From: Dave Taht <dave.taht@gmail.com>
To: David Collier-Brown <davecb@spamcop.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] some benchmarks from arstechnica
Date: Thu, 19 Dec 2019 15:27:04 -0800 [thread overview]
Message-ID: <CAA93jw7G3yAezGRAOm-quLpNwgZJUbLQE+QMZgsCyUHZscTwrA@mail.gmail.com> (raw)
In-Reply-To: <0151ae7d-6416-cf90-f13a-72dc26895d56@rogers.com>
On Thu, Dec 19, 2019 at 3:02 PM David Collier-Brown <davecb.42@gmail.com> wrote:
>
> 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 (;-))
I'm not going to complain (much)! I am totally delighted not only by
the quality of the articles themselves, but by the comments of the
audience, which show an appreciation for reduced latency. Similarly,
tim's work over here is stellar:
https://www.snbforums.com/threads/wi-fi-6-performance-roundup-five-routers-tested.59813/
- journalism, calling to task all the marketing claims, on the web! Am
I dreaming?
I did ask jim for clarification as to his methodology, here:
https://arstechnica.com/gadgets/2019/12/amazons-inexpensive-eero-mesh-wi-fi-kit-is-shockingly-good/?comments=1&post=38427799
And I hope we can make a dent in ax next year!
> 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.
yea...
>
> --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
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
prev parent reply other threads:[~2019-12-19 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 19:32 Dave Taht
2019-12-19 23:02 ` David Collier-Brown
2019-12-19 23:27 ` Dave Taht [this message]
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=CAA93jw7G3yAezGRAOm-quLpNwgZJUbLQE+QMZgsCyUHZscTwrA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.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