From: Taraldsen Erik <erik.taraldsen@telenor.no>
To: "Bjørn Ivar Teigen" <bjorn@domos.no>,
"Michael Richardson" <mcr@sandelman.ca>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] PhD thesis with results related to buffering needs on variable-capacity links
Date: Wed, 4 Jan 2023 07:08:32 +0000 [thread overview]
Message-ID: <34D429F1-188D-4377-B7AB-9B7F06A4AB61@telenor.no> (raw)
In-Reply-To: <CAKf5G6L0=NRHugrQcwiqrM4s0QEtwsg0BPbF9GCtW9TmWDRRpw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
Through my work in Domos I have at least some insight into this. My impression is that it starts with business decisions, where the focus has been on maximum throughput numbers because that's what consumers think they want. It also takes effort, focus, and (most importantly) money to remove bufferbloat, so unless there is sufficient incentives from the commercial side of things it doesn't happen.
I do think there is increasing awareness of latency (under load) as an important factor for user experience. We certainly see that from some of the (dare I say thought-leading) ISPs we're working with.
I think there's hope we will see more good low-latency solutions deployed in the near future.
I’m hoping that you get good traction and market visibility on the latency with your ISP work. Perhaps that will inspire the management in some other ISP’s in you region…
-Erik
[-- Attachment #2: Type: text/html, Size: 2871 bytes --]
next prev parent reply other threads:[~2023-01-04 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 9:57 Bjørn Ivar Teigen
2023-01-03 15:08 ` Michael Richardson
2023-01-03 16:41 ` Bjørn Ivar Teigen
2023-01-04 7:08 ` Taraldsen Erik [this message]
2023-01-03 23:52 ` Toke Høiland-Jørgensen
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=34D429F1-188D-4377-B7AB-9B7F06A4AB61@telenor.no \
--to=erik.taraldsen@telenor.no \
--cc=bjorn@domos.no \
--cc=bloat@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
/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