From: Sebastian Moeller <moeller0@gmx.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: Y via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] random window into other people's latency experience
Date: Sat, 13 Jun 2020 22:05:25 +0200 [thread overview]
Message-ID: <DF86CF57-445A-4187-96A8-46FBA826267D@gmx.de> (raw)
In-Reply-To: <20200611225718.GA32164@aether.stupidest.org>
Hi Chris,
some details below.
> On Jun 12, 2020, at 00:57, Chris Wedgwood <cw@f00f.org> wrote:
>
> the graph/bitmap it creates is actually quite terse but also useful at
> the same time
It is like smokeping for a non-tech audience...
>
> how often does it probe? (i'm curious about the number of data-points
> per pixel)
According to https://www.thinkbroadband.com/faq/broadband-quality-monitor they send an ICMP echo request (aka ping) once every second and each horizontal pixel seems to aggregate 100 seconds.
Best Regards
Sebastian
prev parent reply other threads:[~2020-06-13 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 10:01 Sebastian Moeller
2020-06-10 20:41 ` Jonathan Foulkes
2020-06-11 22:57 ` Chris Wedgwood
2020-06-13 20:05 ` Sebastian Moeller [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=DF86CF57-445A-4187-96A8-46FBA826267D@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=cw@f00f.org \
/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