From: Simon Barber <simon@superduper.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Sina Khanifar <sina@waveform.com>, <sam@waveform.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Updated Bufferbloat Test
Date: Thu, 25 Feb 2021 05:53:36 -0800 [thread overview]
Message-ID: <177d9776300.27a9.e972a4f4d859b00521b2b659602cb2f9@superduper.net> (raw)
In-Reply-To: <alpine.DEB.2.20.2102251445030.21306@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
So perhaps this can feed into the rating system, total latency < 50mS is an
A, < 150mS is a B, 600mS is a C or something like that.
Simon
On February 25, 2021 5:49:26 AM Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Thu, 25 Feb 2021, Simon Barber wrote:
>
>> The ITU say voice should be <150mS, however in the real world people are
>> a lot more tolerant. A GSM -> GSM phone call is ~350mS, and very few
>> people complain about that. That said the quality of the conversation is
>> affected, and staying under 150mS is better for a fast free flowing
>> conversation. Most people won't have a problem at 600mS and will have a
>> problem at 1000mS. That is for a 2 party voice call. A large group
>> presentation over video can tolerate more, but may have issues with
>> talking over when switching from presenter to questioner for example.
>
> I worked at a phone company 10+ years ago. We had some equipment that
> internally was ATM based and each "hop" added 7ms. This in combination
> with IP based telephony at the end points that added 40ms one-way per
> end-point (PDV buffer) caused people to complain when RTT started creeping
> up to 300-400ms. This was for PSTN calls.
>
> Yes, people might have more tolerance with mobile phone calls because they
> have lower expectations when out and about, but my experience is that
> people will definitely notice 300-400ms RTT but they might not get upset
> enough to open a support ticket until 600ms or more.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
[-- Attachment #2: Type: text/html, Size: 2823 bytes --]
next prev parent reply other threads:[~2021-02-25 13:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 18:22 Sina Khanifar
2021-02-24 22:10 ` Dave Taht
2021-02-24 23:39 ` Simon Barber
2021-02-25 5:56 ` Sina Khanifar
2021-02-25 7:15 ` Simon Barber
2021-02-25 7:32 ` Sina Khanifar
2021-02-25 13:38 ` Simon Barber
2021-02-25 13:43 ` Dave Taht
2021-02-25 13:49 ` Mikael Abrahamsson
2021-02-25 13:53 ` Simon Barber [this message]
2021-02-25 19:47 ` Sina Khanifar
2021-02-25 19:56 ` Simon Barber
2021-02-25 20:10 ` Sina Khanifar
2021-02-25 20:52 ` Simon Barber
2021-02-25 20:53 ` Simon Barber
2021-02-25 13:46 ` Simon Barber
2021-02-25 7:20 ` Simon Barber
2021-02-25 10:51 ` Sebastian Moeller
2021-02-25 20:01 ` Sina Khanifar
2021-02-25 20:14 ` Sebastian Moeller
2021-02-26 1:06 ` Daniel Lakeland
2021-02-26 8:20 ` Sina Khanifar
2021-02-26 17:25 ` Michael Richardson
2021-02-24 22:15 ` Kenneth Porter
2021-02-25 5:29 ` Kenneth Porter
2021-02-25 5:35 ` Dave Taht
2021-02-25 6:24 ` Kenneth Porter
2021-02-25 1:16 ` David Collier-Brown
2021-02-25 6:21 ` Sina Khanifar
2021-02-25 4:48 ` Marco Belmonte
[not found] ` <1D68EF40C3A8A269831408C8@172.27.17.193>
2021-02-25 5:58 ` Sina Khanifar
2021-02-25 9:47 ` Mikael Abrahamsson
2021-02-25 10:49 ` Sebastian Moeller
2021-02-25 20:41 ` Sina Khanifar
2021-02-25 20:50 ` Sina Khanifar
2021-02-25 21:15 ` Sebastian Moeller
2021-02-26 8:23 ` Sina Khanifar
2021-02-26 18:41 ` Sina Khanifar
2021-02-26 19:58 ` Sebastian Moeller
2021-02-25 12:27 ` Toke Høiland-Jørgensen
2021-02-25 14:48 ` 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=177d9776300.27a9.e972a4f4d859b00521b2b659602cb2f9@superduper.net \
--to=simon@superduper.net \
--cc=bloat@lists.bufferbloat.net \
--cc=sam@waveform.com \
--cc=sina@waveform.com \
--cc=swmike@swm.pp.se \
/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