[Bloat] some benchmarks from arstechnica

[Bloat] some benchmarks from arstechnica

[Dave Taht]

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

-- 
Make Music, Not War

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729

Re: [Bloat] some benchmarks from arstechnica

[David Collier-Brown]

[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]

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


[-- Attachment #2: Type: text/html, Size: 3964 bytes --]

Re: [Bloat] some benchmarks from arstechnica

[Dave Taht]

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