From: Eric <evil.function@proton.me>
To: Rich Brown <richb.hanover@gmail.com>
Cc: Rich Brown via Bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Re: Cutie Network Quality Test now in alpha-test
Date: Mon, 27 Oct 2025 16:54:03 +0000 [thread overview]
Message-ID: <-VaUY0C96Y7FEO6D1ewDWjig_2r_WttxUzz_qcz3BAk30RmmqtNFXwdwLef9wbe2SUeps2YGuw5i4YLAyksIfPukrXQMcml5dvqBp99qbzk=@proton.me> (raw)
In-Reply-To: <277398AE-EB13-422B-B645-DEAA62C8D312@gmail.com>
On Monday, October 27th, 2025 at 07:47, Rich Brown <richb.hanover@gmail.com> wrote:
> With some trepidation (and a little bit of pride), I announce the Cutie network quality test. Inspired by the VSee Network Stability Test, Cutie is a completely new implementation of that concept that establishes a WebRTC connection to its backend server, then uses the RTC stream (10 messages per second) to measure and chart latency, jitter, and packet loss.
>
> You can try the demo site at: netperf.bufferbloat.net:5173 http://netperf.bufferbloat.net:5173/ or you can install Cutie on a local server to test your own network.
>
>
> There’s lots more information in the Github repo at: https://github.com/richb-hanover/Cutie-Network-Quality-Test
Hey Rich,
Are you ready to list it on Sebastian's testing thread?
https://forum.openwrt.org/t/2025-current-recommendations-for-bufferbloat-testing/241303
Eric
next prev parent reply other threads:[~2025-10-27 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 14:46 [Bloat] " Rich Brown
2025-10-27 15:58 ` [Bloat] " Sebastian Moeller
2025-10-27 16:38 ` Frantisek Borsik
2025-10-27 16:54 ` Eric [this message]
2025-10-28 3:08 ` Rich Brown
[not found] ` <MW4PR11MB71047059F01078746A3F27E4C7FAA@MW4PR11MB7104.namprd11.prod.outlook.com>
2025-10-30 2:11 ` Rich Brown
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='-VaUY0C96Y7FEO6D1ewDWjig_2r_WttxUzz_qcz3BAk30RmmqtNFXwdwLef9wbe2SUeps2YGuw5i4YLAyksIfPukrXQMcml5dvqBp99qbzk=@proton.me' \
--to=evil.function@proton.me \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
/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