From: Michael Welzl <michawe@ifi.uio.no>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] DOCSIS 3+ recommendation?
Date: Fri, 20 Mar 2015 21:59:37 +0100 [thread overview]
Message-ID: <4C566C48-769A-4AC9-910F-B852EBF4B7A8@ifi.uio.no> (raw)
In-Reply-To: <2E2D6622-1791-4CBB-856E-CE7BA39D99E0@gmail.com>
> On 20. mar. 2015, at 17.31, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>
>> On 20 Mar, 2015, at 16:54, Michael Welzl <michawe@ifi.uio.no> wrote:
>>
>> I'd like people to understand that packet loss often also comes with delay - for having to retransmit.
>
> Or, turning it upside down, it’s always a win to drop packets (in the service of signalling congestion) if the induced delay exceeds the inherent RTT.
Actually, no: as I said, the delay caused by a dropped packet can be more than 1 RTT - even much more under some circumstances. Consider this quote from the intro of https://tools.ietf.org/html/draft-dukkipati-tcpm-tcp-loss-probe-01 :
***
To get a sense of just how long the RTOs are in relation to
connection RTTs, following is the distribution of RTO/RTT values on
Google Web servers. [percentile, RTO/RTT]: [50th percentile, 4.3];
[75th percentile, 11.3]; [90th percentile, 28.9]; [95th percentile,
53.9]; [99th percentile, 214].
***
That would be for the unfortunate case where you drop a packet at the end of a burst and you don't have TLP or anything, and only an RTO helps...
Cheers,
Michael
next prev parent reply other threads:[~2015-03-20 20:59 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 20:35 [Cerowrt-devel] " Matt Taggart
2015-03-17 23:32 ` Valdis.Kletnieks
2015-03-18 4:34 ` David P. Reed
2015-03-18 6:26 ` Jonathan Morton
2015-03-18 19:38 ` JF Tremblay
2015-03-18 19:50 ` Jonathan Morton
2015-03-19 13:53 ` dpreed
2015-03-19 14:11 ` JF Tremblay
2015-03-19 15:38 ` dpreed
2015-03-19 15:40 ` Jim Gettys
2015-03-19 17:04 ` Michael Richardson
2015-03-19 17:14 ` Jonathan Morton
2015-03-19 17:11 ` Dave Taht
2015-03-19 19:58 ` [Cerowrt-devel] [Bloat] " Livingood, Jason
2015-03-19 20:29 ` dpreed
2015-03-19 23:18 ` Greg White
2015-03-20 8:18 ` MUSCARIELLO Luca IMT/OLN
2015-03-20 13:31 ` David P. Reed
2015-03-20 13:46 ` Sebastian Moeller
2015-03-20 14:05 ` MUSCARIELLO Luca IMT/OLN
2015-03-20 10:07 ` Sebastian Moeller
2015-03-20 13:50 ` [Cerowrt-devel] Latency Measurements in Speed Test suites (was: DOCSIS 3+ recommendation?) Rich Brown
2015-03-29 17:36 ` [Cerowrt-devel] [Bloat] " Pedro Tumusok
2015-03-30 7:06 ` Jonathan Morton
2015-03-20 13:57 ` [Cerowrt-devel] [Bloat] DOCSIS 3+ recommendation? Livingood, Jason
2015-03-20 14:08 ` David P. Reed
2015-03-20 14:14 ` MUSCARIELLO Luca IMT/OLN
2015-03-20 14:48 ` Matt Mathis
2015-03-20 18:04 ` Valdis.Kletnieks
2015-03-20 13:48 ` Jim Gettys
2015-03-20 14:11 ` Livingood, Jason
2015-03-20 14:54 ` Michael Welzl
2015-03-20 15:31 ` Jim Gettys
2015-03-20 15:39 ` Michael Welzl
2015-03-20 16:31 ` Jonathan Morton
2015-03-20 20:59 ` Michael Welzl [this message]
2015-03-20 23:47 ` David P. Reed
2015-03-21 0:08 ` Michael Welzl
2015-03-21 0:03 ` David Lang
2015-03-21 0:13 ` Steinar H. Gunderson
2015-03-21 0:25 ` David Lang
2015-03-21 0:34 ` Jonathan Morton
2015-03-21 0:38 ` David Lang
2015-03-21 0:43 ` Jonathan Morton
2015-03-22 4:15 ` Michael Welzl
2015-03-21 0:15 ` Michael Welzl
2015-03-21 0:29 ` David Lang
2015-03-22 4:10 ` Michael Welzl
2015-03-20 18:14 ` Jonathan Morton
2015-03-18 8:06 ` [Cerowrt-devel] " Sebastian Moeller
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C566C48-769A-4AC9-910F-B852EBF4B7A8@ifi.uio.no \
--to=michawe@ifi.uio.no \
--cc=Jason_Livingood@cable.comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.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