CoDel AQM discussions
 help / color / mirror / Atom feed
From: "Nils Andreas Svee" <me@lochnair.net>
To: "the keyboard of geoff goodfellow" <geoff@iconia.com>,
	"Frantisek Borsik" <frantisek.borsik@gmail.com>
Cc: "Jeremy Austin" <rpm@lists.bufferbloat.net>,
	"Herbert Wolverson" <hwolverson@libreqos.io>,
	libreqos <libreqos@lists.bufferbloat.net>,
	"Dave Taht" <starlink@lists.bufferbloat.net>,
	codel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>,
	"Cake List" <cake@lists.bufferbloat.net>,
	bloat-ietf@lists.bufferbloat.net,
	"Robert Chacón" <robert@libreqos.io>
Subject: Re: [Codel] [Bloat] [Starlink] Announcing the LibreQoS Bufferbloat TestPlatform
Date: Sun, 15 Jun 2025 23:52:46 +0700	[thread overview]
Message-ID: <6684dff4-c2a1-4f41-be9a-71162f256031@app.fastmail.com> (raw)
In-Reply-To: <CAEf-zriqpW5Feyj-eRBiX7xiozy43n5Gkr7CvrjVYT-+RwvgfQ@mail.gmail.com>

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

Just tried it too: https://imgur.com/a/F2cNZd4, also getting A+ overall, and "only" A for bidirectional.

I seem to be getting a 200+ ms spike right at the beginning of the baseline test, which skews the results.
This happened at least on a couple of tests, but after a few tries it got better. At least with ICMP ping separately I don't see any spikes like that.

Best Regards
Nils

On Sun, Jun 15, 2025, at 23:20, the keyboard of geoff goodfellow via Bloat wrote:
> re: *thoughts and feedback!*
> 
> your https://test.libreqos.com tests of [Single User Test] & [Virtual Household Mode] both give yours truly bufferbloat grades of *A+ *
> 
> whereas the https://www.waveform.com/tools/bufferbloat test gives yours truly a bufferbloat brade grade of *C*
> 
> https://www.waveform.com/tools/bufferbloat?test-id=b13810f2-e999-4045-8e8b-ab3ab8b957c5
> 
> #1.) Why/What's the difference?
> 
> #2.) Who/Which one to believe¿
> 
> g
> 
> 
> On Sun, Jun 15, 2025 at 4:58 AM Frantisek Borsik via Starlink <starlink@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
>> 
>> *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 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
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
> 
> 
> --
> Geoff.Goodfellow@iconia.com
> 
> living as The Truth is True
> 
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
> 

[-- Attachment #2: Type: text/html, Size: 11469 bytes --]

  reply	other threads:[~2025-06-15 16:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-15 12:00 [Codel] Announcing the LibreQoS Bufferbloat Test Platform Frantisek Borsik
2025-06-15 16:20 ` [Codel] [Starlink] " the keyboard of geoff goodfellow
2025-06-15 16:52   ` Nils Andreas Svee [this message]
2025-06-15 17:32     ` [Codel] [Cake] [Bloat] [Starlink] Announcing the LibreQoS Bufferbloat TestPlatform dave seddon
2025-06-15 18:05       ` Robert Chacón
2025-06-15 20:12         ` dave seddon
2025-06-15 17:27   ` [Codel] [Starlink] Announcing the LibreQoS Bufferbloat Test Platform J Pan
2025-06-15 19:23 ` [Codel] [Bloat] " Michael Richardson
2025-06-16 19:03 ` [Codel] [Cake] " David P. Reed
2025-06-17 15:27 ` [Codel] [Bloat] " jf

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/codel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6684dff4-c2a1-4f41-be9a-71162f256031@app.fastmail.com \
    --to=me@lochnair.net \
    --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=geoff@iconia.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