From: Pete Heist <peteheist@gmail.com>
To: flent-users <flent-users@flent.org>
Subject: Re: [Flent-users] SmokePing probe
Date: Sun, 18 Feb 2018 12:35:46 +0100 [thread overview]
Message-ID: <7E95C080-5DA6-4CD9-829A-C01D74F531E7@gmail.com> (raw)
In-Reply-To: <8B3FF5BA-2219-466D-B02E-C5B0C6EF0CD9@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1624 bytes --]
The author pulled the probe in pretty quickly, so it’s already upstream. Some samples:
https://www.drhleny.cz/bufferbloat/smokeping/irtt_smokeping.png <https://www.drhleny.cz/bufferbloat/smokeping/irtt_smokeping.png>
https://www.drhleny.cz/bufferbloat/smokeping/irtt_smokeping2.png <https://www.drhleny.cz/bufferbloat/smokeping/irtt_smokeping2.png>
Maybe I’ll post another image after a while if something more exciting happens… :)
> On Feb 18, 2018, at 12:29 AM, Pete Heist <peteheist@gmail.com> wrote:
>
> I wrote a SmokePing (https://oss.oetiker.ch/smokeping/) probe for IRTT:
>
> Code: https://github.com/peteheist/SmokePing/blob/master/lib/Smokeping/probes/IRTT.pm
>
> Pull request: https://github.com/oetiker/SmokePing/pull/110
>
> I hope to use this in my ISP, which uses SmokePing for about 70 access points. Since ICMP is apparently being prioritized, I don’t think the current SmokePing graphs are telling much of a story about queueing delay.
>
> I’ve been mesmerized for the past couple hours watching one-way delay stats. The link I’m testing is 3km NLOS point-to-point WiFi, with trees about 100 meters from my side of the link. When there is delay or loss, it’s almost always on sending (from me). Median send IPDV (jitter) is around 5x that of the receive IPDV. Presumably, the scattering due to the trees is worse on the uplink because the signal hits the trees closer to the transmitter, when it still has a longer distance to travel. This may also explain my 10/30 asymmetric throughput. I thought about trimming these trees, but this is too much fun… :)
>
[-- Attachment #1.2: Type: text/html, Size: 2605 bytes --]
[-- Attachment #2: Type: text/plain, Size: 151 bytes --]
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
prev parent reply other threads:[~2018-02-18 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 23:29 Pete Heist
2018-02-18 11:35 ` Pete Heist [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.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7E95C080-5DA6-4CD9-829A-C01D74F531E7@gmail.com \
--to=peteheist@gmail.com \
--cc=flent-users@flent.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