From: Jonathan Foulkes <jf@jonathanfoulkes.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
Adam Hunt <adam.r.hunt@gmail.com>,
jgc@cloudflare.com, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] New speed/latency/jitter test site from Cloudflare
Date: Wed, 3 Jun 2020 16:46:21 -0400 [thread overview]
Message-ID: <1EC5523E-B2B9-4AE8-93EC-37A2E7A49FE5@jonathanfoulkes.com> (raw)
In-Reply-To: <1C65A8E8-3685-4DCB-ABC1-0AF353EA0E5B@gmail.com>
Jonathan, if you download the csv of the results, it seems to have latency metrics interspersed with the payloads, but since I run Cake on all the time, can’t really see much of a change in latencies ;-)
And one more hearty vote for an upload test with latency under load metrics as well.
And thanks Cloudflare for making the details of the test retrievable for further analysis or historical record keeping.
Cheers,
Jonathan Foulkes
> On Jun 3, 2020, at 4:22 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 3 Jun, 2020, at 7:48 pm, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I am of course, always interested in how they are measuring latency, and where.
>
> They don't seem to be adding more latency measurements once the download tests begin. So in effect they are only measuring idle latency.
>
> - Jonathan Morton
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2020-06-03 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 10:49 Adam Hunt
2020-06-03 11:34 ` Toke Høiland-Jørgensen
[not found] ` <mailman.483.1591184067.24343.bloat@lists.bufferbloat.net>
2020-06-03 16:48 ` Dave Taht
2020-06-03 20:22 ` Jonathan Morton
2020-06-03 20:46 ` Jonathan Foulkes [this message]
2020-06-04 9:51 ` Toke Høiland-Jørgensen
2020-06-04 10:07 ` John Graham-Cumming
2020-06-04 15:41 ` Dave Taht
2020-06-04 16:09 ` John Graham-Cumming
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=1EC5523E-B2B9-4AE8-93EC-37A2E7A49FE5@jonathanfoulkes.com \
--to=jf@jonathanfoulkes.com \
--cc=adam.r.hunt@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=jgc@cloudflare.com \
/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