From: John Graham-Cumming <jgc@cloudflare.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Jonathan Morton <chromatix99@gmail.com>,
Dave Taht <dave.taht@gmail.com>,
Adam Hunt <adam.r.hunt@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] New speed/latency/jitter test site from Cloudflare
Date: Thu, 4 Jun 2020 11:07:18 +0100 [thread overview]
Message-ID: <CAJYXS=Tjc35WV76isSrLmYFe4a4tg2vSb8fMhZEAu=3kHmU3QQ@mail.gmail.com> (raw)
In-Reply-To: <87v9k7jgzo.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
We're definitely open to changing the speed test. It's being actively
worked on. Issues through GitHub probably the best way to engage, but I'm
happy to get direct email also.
On Thu, 4 Jun 2020 at 10:51, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Jonathan Morton <chromatix99@gmail.com> writes:
>
> >> 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.
>
> Yup, but they do seem to be amenable to fixing that:
> https://github.com/cloudflare/worker-speedtest-template/issues/13
>
> As for where the latency is measured to, it seems to be HTTP 'pings' to
> the nearest Cloudflare CDN endpoint.
>
> -Toke
>
[-- Attachment #2: Type: text/html, Size: 1497 bytes --]
next prev parent reply other threads:[~2020-06-04 10:07 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
2020-06-04 9:51 ` Toke Høiland-Jørgensen
2020-06-04 10:07 ` John Graham-Cumming [this message]
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='CAJYXS=Tjc35WV76isSrLmYFe4a4tg2vSb8fMhZEAu=3kHmU3QQ@mail.gmail.com' \
--to=jgc@cloudflare.com \
--cc=adam.r.hunt@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=toke@toke.dk \
/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