From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id A6FD53B29E for ; Thu, 4 Jun 2020 05:51:59 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1591264317; bh=cOL3Gp97jK6EOUXMHdfZUOBAi2rqWsvSx9YGZ9UmIjY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=E0ebzaJZlqdpsP9UdZ40YgjwiuiKgduUI5i46W4dL+xq0IaWOv+awlrLMIyWM7H1b ++46pxMQlt4jBcUbqv0xBlO+7C4BxIVkZmI+lZCYpgCeU+CWl0Hdur/MilKet4WlsT eN0wLXV2sZFHyT8fsRc+zXRMrXF2lXtfWAB69iW1UeV042y4B+Hzij7mByRsaSpwJQ 00o0ZLGnXukkdwqCCVyDhW+zth9V5efzOoV1r9rj623TMr6Tt197QbO5MqqKoOplpN K3Ff7k0VHoXn1/NpQ6iDSvaz1QFO/OqNk8LCnVZ5cJRTVA6vyzd55WgikKdr7NlU02 qtbm6XBgMilBg== To: Jonathan Morton , Dave Taht Cc: Adam Hunt , jgc@cloudflare.com, bloat Subject: Re: [Bloat] New speed/latency/jitter test site from Cloudflare In-Reply-To: <1C65A8E8-3685-4DCB-ABC1-0AF353EA0E5B@gmail.com> References: <1C65A8E8-3685-4DCB-ABC1-0AF353EA0E5B@gmail.com> Date: Thu, 04 Jun 2020 11:51:55 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87v9k7jgzo.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain X-List-Received-Date: Thu, 04 Jun 2020 09:51:59 -0000 Jonathan Morton writes: >> On 3 Jun, 2020, at 7:48 pm, Dave Taht 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