From: Rich Brown <richb.hanover@gmail.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: Rich Brown via Bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Re: Cutie Network Quality Test now in alpha-test
Date: Wed, 29 Oct 2025 22:11:51 -0400 [thread overview]
Message-ID: <059E88BC-96B7-4CD4-860E-0519B08FB096@gmail.com> (raw)
In-Reply-To: <MW4PR11MB71047059F01078746A3F27E4C7FAA@MW4PR11MB7104.namprd11.prod.outlook.com>
Hi Jason,
Thanks for checking out Cutie. I’m glad it worked for you. It still needs to beef up the server side - it keeps going to sleep after an indeterminate time. I just added more logging.
Rich
> On Oct 29, 2025, at 11:19, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
>
> Very cool! I ran this test via by Comcast cable modem during a Microsoft Teams call with Slack, Chrome, and Outlook in the background.
>
> <Screenshot 2025-10-29 at 11.17.16.png>
> <Screenshot 2025-10-29 at 11.17.42.png>
>
> Latency Monitor
>
> Metric
> Now
> Min
> Max
> 10s Avg
> MOS Quality
> 4.38
> 4.37
> 4.39
> 4.38
> Packet Loss %
> 0.00 %
> 0.00 %
> 0.00 %
> 0.00 %
> Latency
> 30.20 ms
> 24.80 ms
> 49.00 ms
> 35.49 ms
> Jitter
> 5.51 ms
> 0.00 ms
> 7.80 ms
>
>
>
> From: Rich Brown <richb.hanover@gmail.com>
> Date: Monday, October 27, 2025 at 10:47
> To: Rich Brown via Bloat <bloat@lists.bufferbloat.net>
> Cc: Richard Brown <richb.hanover@gmail.com>
> Subject: [Bloat] Cutie Network Quality Test now in alpha-test
>
> 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 <https://urldefense.com/v3/__http://netperf.bufferbloat.net:5173/__;!!CQl3mcHX2A!DGUep6rbrYzzIVRDl8vYGmBVcGxpubYs8I8vL2DfN0UmEK9i1Uq5wStI-5RW2ZacTNPoEl8E-U0FKahU77MAjs1VJ8IGTg$ > 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://urldefense.com/v3/__https://github.com/richb-hanover/Cutie-Network-Quality-Test__;!!CQl3mcHX2A!DGUep6rbrYzzIVRDl8vYGmBVcGxpubYs8I8vL2DfN0UmEK9i1Uq5wStI-5RW2ZacTNPoEl8E-U0FKahU77MAjs1we3rw_w$
>
> Comments and bug reports welcome. Enjoy!
>
> Rich
>
> PS Why “Cutie”? It’s a vaguely humorous pronunciation of “QT” for Quality Test...
> _______________________________________________
> Bloat mailing list -- bloat@lists.bufferbloat.net
> To unsubscribe send an email to bloat-leave@lists.bufferbloat.net
prev parent reply other threads:[~2025-10-30 2:12 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
2025-10-28 3:08 ` Rich Brown
[not found] ` <MW4PR11MB71047059F01078746A3F27E4C7FAA@MW4PR11MB7104.namprd11.prod.outlook.com>
2025-10-30 2:11 ` Rich Brown [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=059E88BC-96B7-4CD4-860E-0519B08FB096@gmail.com \
--to=richb.hanover@gmail.com \
--cc=Jason_Livingood@comcast.com \
--cc=bloat@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