General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: David Collier-Brown <davec-b@rogers.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] An ACM Queue article about bloat and LibraQoS
Date: Mon, 15 Jul 2024 15:12:47 +0200	[thread overview]
Message-ID: <FD5DC215-83C7-4628-ADF0-FF011F730BC1@gmx.de> (raw)
In-Reply-To: <b5973f9e-c236-4c5a-979b-6ac451149c9a@rogers.com>

Hi Dave,


> On 15. Jul 2024, at 12:59, David Collier-Brown via Bloat <bloat@lists.bufferbloat.net> wrote:
> 
> On 2024-07-15 05:18, Sebastian Moeller via Bloat wrote:
>> Hi Dave,
>> 
>> nice! I only would have wished for the A-grade waveform result as well, it is a bit of a downer that the last figure show the unpleasant 'before' status only.
>> 
>> Regards
>> Sebastian
> 
> That was a deliberate action on my part: the "after" status shows much smaller throughput numbers, leading observant readers to ask if improving latency didn't destroy one's bandwidth.

	[SM] Ah, I see. But just for our discussion here, how much (potential) capacity did you need to treade in for decent responsiveness?

> I suspect that the throughputs "with bloat" are greatly exaggerated... from counting the extra data that fills the bloated buffers (;-))

	[SM] Good point... especially for upload tests, I occasionally see numbers which I know for a fact to be impossible (abovre the gross capacity of my access link) and I wonder whether all tests actually do proper reporting of the grand average capacity numbers. This should not be rocket science: take the start time of the first maesasurement flow and the end time of the last measurement flow and divide the total number of payload bytes trasferred by the total time this took. 

> 
> --dave
> 
> 
>> 
>>> On 14. Jul 2024, at 23:30, David Collier-Brown via Bloat <bloat@lists.bufferbloat.net> wrote:
>>> 
>>> I have a new article on ACM Queue, at https://dl.acm.org/doi/pdf/10.1145/3674953
>>> "If you're an ISP and all your customers hate you, take heart. This is now a solvable problem."
>>> It's part of a tongue-in-cheek series called "You Don't Know Jack", and it's about Bufferbloat and the LibreQoS project.
>>> --dave
>>> -- 
>>> David Collier-Brown, | Always do right. This will gratify
>>> System Programmer and Author | some people and astonish the rest
>>> davecb@spamcop.net | -- Mark Twain
>>> _______________________________________________
>>> Bloat mailing list
>>> Bloat@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/bloat
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
> 
> -- 
> David Collier-Brown,         | Always do right. This will gratify
> System Programmer and Author | some people and astonish the rest
> davecb@spamcop.net           |              -- Mark Twain
> 
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


  reply	other threads:[~2024-07-15 13:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA93jw7beHsoUkDKYhRB0S3VhU5UHbhvGNnTvfN1b37LqyXKhg@mail.gmail.com>
     [not found] ` <9B529996-9FF0-4487-8F74-B01230E6FCA1@viagenie.ca>
     [not found]   ` <11567.1720044376@obiwan.sandelman.ca>
     [not found]     ` <CAHn=e4iTz3Jztou-AkKULGVjj5Tm8vy-1cMXXyp9Qd5v5BgORQ@mail.gmail.com>
2024-07-14 21:30       ` David Collier-Brown
2024-07-15  9:18         ` Sebastian Moeller
2024-07-15 10:59           ` David Collier-Brown
2024-07-15 13:12             ` Sebastian Moeller [this message]
2024-07-15 14:26               ` David Collier-Brown
2024-07-16 13:48                 ` Sebastian Moeller
2024-07-16 14:25                   ` David Collier-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=FD5DC215-83C7-4628-ADF0-FF011F730BC1@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davec-b@rogers.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