General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Rpm <rpm@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Bufferbloat measurements in rust
Date: Sun, 5 Jun 2022 08:48:51 -0700	[thread overview]
Message-ID: <CAA93jw7Q6Aafd57Ezb6RkCM4imDh6Qg=oRVOVFeLbTbOFp3SYA@mail.gmail.com> (raw)
In-Reply-To: <CADari_S8n4vNsLfQVot3QeygwgiX6qw3T4fRGT7-2t3oDd2WiQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

simple tool to measure latency w/load... in RUST! And it works on windows.

https://github.com/Zoxc/rust-latency/

...

Hi there.

I wrote a tool to cause and measure bufferbloat and I thought I'd
share some measurements.

You can see the bufferbloat on the AP side with the download graph for
Unifi AP AC LR and MikroTik cAP ac.

Anything sent from Windows has bad bufferbloat.

'Realtek Wired Linux to 100 Mbps switch.png' shows how effective
fq_codel is on the host with the upload graph and the download graph
shows the fixed buffer size of the 100 Mbps switch.

Thanks,
John



-- 
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC

[-- Attachment #2: Intel AX210 Windows to MikroTik cAP ac 5 Ghz.png --]
[-- Type: image/png, Size: 241834 bytes --]

[-- Attachment #3: Realtek Wired Windows to 100 Mbps switch.png --]
[-- Type: image/png, Size: 120402 bytes --]

[-- Attachment #4: Realtek Wired Linux to 100 Mbps switch.png --]
[-- Type: image/png, Size: 132695 bytes --]

[-- Attachment #5: Intel AX210 Windows to Unifi AP AC LR 5 Ghz.png --]
[-- Type: image/png, Size: 183825 bytes --]

           reply	other threads:[~2022-06-05 15:49 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CADari_S8n4vNsLfQVot3QeygwgiX6qw3T4fRGT7-2t3oDd2WiQ@mail.gmail.com>]

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='CAA93jw7Q6Aafd57Ezb6RkCM4imDh6Qg=oRVOVFeLbTbOFp3SYA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=rpm@lists.bufferbloat.net \
    /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