From: "jf@jonathanfoulkes.com" <jf@jonathanfoulkes.com>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
"Dave Taht via Starlink" <starlink@lists.bufferbloat.net>,
"Jeremy Austin via Rpm" <rpm@lists.bufferbloat.net>,
bloat-ietf@lists.bufferbloat.net,
"Cake List" <cake@lists.bufferbloat.net>,
codel@lists.bufferbloat.net,
"Herbert Wolverson" <hwolverson@libreqos.io>,
"Robert Chacón" <robert@libreqos.io>
Subject: Re: [LibreQoS] [Bloat] Announcing the LibreQoS Bufferbloat Test Platform
Date: Tue, 17 Jun 2025 11:27:31 -0400 [thread overview]
Message-ID: <1375C139-D1A8-4755-AB29-28C1AAEC3453@jonathanfoulkes.com> (raw)
In-Reply-To: <CAJUtOOjCYQDdULwY8g0qLgHmBq=0rVCZeYEiokd4kOiip0ED5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5212 bytes --]
First, a huge thank you for this excellent tool; the field needed this one.
Secondly, kudos for giving a nod to our late friend, Dave Taht. My face lit up when I saw the thumbs-up icon on the A+ result!
I instantly recognized him. Thank you so much for this; well done.

My household test result

Cheers,
Jonathan Foulkes
> On Jun 15, 2025, at 8:00 AM, Frantisek Borsik via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> Hello to all,
>
> We're excited to announce the release of the LibreQoS Bufferbloat Test – an open-source bufferbloat testing solution designed specifically for ISPs and network operators to deploy for their customers.
>
> Link
> https://test.libreqos.com <https://test.libreqos.com/>
>
> What Makes This Different
>
> While there are several bufferbloat testing tools available, this platform addresses a critical gap: ISP-deployable infrastructure that provides both traditional testing and realistic household simulation.
>
> As Dave Täht highlighted in his influential article "What's Wrong with Speed Tests" <https://blog.cerowrt.org/post/speedtests/>, traditional speed tests fail to measure what users actually experience. We tried to address Dave's points to make a better speed test that focuses on the metric that matters: latency under load in realistic usage scenarios.
>
> Two Complementary Test Modes
>
> Single User Test Mode
> Traditional sequential load testing (baseline → download → upload → bidirectional)
> Measures working latency and jitter during each phase
> Familiar A+ to F grading based on latency under load increases
> Comparable to existing tools like DSLReports Speed Test and Waveform Bufferbloat Test
>
> Virtual Household Mode (The Innovation)
>
> Process-isolated simulation of 4 concurrent users with authentic traffic patterns:
> Alex (Gaming): 1.5 Mbps constant, jitter-sensitive for competitive gaming
> Sarah (Video Conference): 2.5 Mbps bidirectional, Teams simulation with working latency monitoring
> Jake (Netflix HD): 25 Mbps bursts (1s on, 4s off), realistic streaming patterns
> Computer (Background): Up to 200 Mbps continuous download, system updates
>
> Real-world relevance: Tests latency under load when multiple family members are online simultaneously
>
> Advanced grading: Network fairness, jitter measurement, and per-user working latency analysis
>
> Why (not only) ISPs Need This
>
> The traditional approach of sending customers to third-party speed test sites has limitations:
> No control over test methodology or server placement
> Limited correlation with customer support tickets
> Generic results that don't reflect real-world usage patterns
> No integration with ISP operational systems
> This platform enables (not only) ISPs to:
> Host their own testing infrastructure with full control
> Integrate with support systems via telemetry APIs
> Provide customers with realistic household testing scenarios
> Correlate test results with network performance and customer complaints
>
> Open Source & Community
>
> The entire platform is open source and available here: https://github.com/LibreQoE/bufferbloat_test
>
> We've designed this to be:
> Easy to deploy for (not only) ISPs of any size
> Scientifically meaningful in its measurement methodology
> Realistic in its simulation of actual household usage
> Integrable with existing ISP operational workflows
>
> Community Feedback Requested
>
> We'd love feedback from the bufferbloat.net <http://bufferbloat.net/> community on:
> Test methodology: Are we measuring the right metrics?
> Grading thresholds: Do our A+ to F grades align with real-world impact?
> Virtual household scenarios: What other realistic usage patterns should we simulate?
> ISP adoption: What barriers exist for ISP deployment?
>
> Technical Discussion
>
> We'd welcome discussion about:
> Measurement accuracy for working latency and jitter in virtual household mode
> Traffic pattern authenticity (gaming, video conferencing, streaming)
> Grading methodology for latency under load in complex multi-user scenarios
> Integration approaches for ISP operational systems
>
> The platform represents our attempt to bridge the gap between academic bufferbloat research and practical ISP operations, building on the foundational work of researchers like Dave Täht and the broader bufferbloat community. We believe that widespread ISP deployment of proper bufferbloat testing infrastructure will ultimately benefit the entire internet ecosystem.
>
> Looking forward to the community's thoughts and feedback!
>
> Best regards,
>
> The LibreQoS Team
>
>
> In loving memory of Dave Täht: 1965-2025
>
> https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
>
>
>
> https://www.linkedin.com/in/frantisekborsik
>
> Signal, Telegram, WhatsApp: +421919416714
>
> iMessage, mobile: +420775230885
>
> Skype: casioa5302ca
>
> frantisek.borsik@gmail.com <mailto:frantisek.borsik@gmail.com>_______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
[-- Attachment #2.1: Type: text/html, Size: 7400 bytes --]
[-- Attachment #2.2: DaveThat_ThumbsUp.png --]
[-- Type: image/png, Size: 36966 bytes --]
[-- Attachment #2.3: LibreQoS-Virtual-Household-Test-Result-2025-06-15.png --]
[-- Type: image/png, Size: 279088 bytes --]
prev parent reply other threads:[~2025-06-17 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 12:00 [LibreQoS] " Frantisek Borsik
2025-06-15 16:20 ` [LibreQoS] [Starlink] " the keyboard of geoff goodfellow
2025-06-15 16:52 ` [LibreQoS] [Bloat] [Starlink] Announcing the LibreQoS Bufferbloat TestPlatform Nils Andreas Svee
2025-06-15 17:32 ` [LibreQoS] [Cake] " dave seddon
2025-06-15 18:05 ` Robert Chacón
2025-06-15 20:12 ` dave seddon
2025-06-15 17:27 ` [LibreQoS] [Starlink] Announcing the LibreQoS Bufferbloat Test Platform J Pan
2025-06-15 19:23 ` [LibreQoS] [Bloat] " Michael Richardson
2025-06-16 19:03 ` [LibreQoS] [Cake] " David P. Reed
2025-06-17 15:27 ` jf [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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1375C139-D1A8-4755-AB29-28C1AAEC3453@jonathanfoulkes.com \
--to=jf@jonathanfoulkes.com \
--cc=bloat-ietf@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=frantisek.borsik@gmail.com \
--cc=hwolverson@libreqos.io \
--cc=libreqos@lists.bufferbloat.net \
--cc=robert@libreqos.io \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@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