From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mout.perfora.net", Issuer "Thawte SSL CA" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 7975221F64A for ; Fri, 29 Aug 2014 09:54:13 -0700 (PDT) Received: from J4 (c-68-50-226-187.hsd1.md.comcast.net [68.50.226.187]) by mrelay.perfora.net (node=mreueus003) with ESMTP (Nemesis) id 0MfGQe-1XmDiU2oAs-00OoOL; Fri, 29 Aug 2014 18:54:11 +0200 From: "Jerry Jongerius" To: "'Jonathan Morton'" References: <000001cfbefe$69194c70$3b4be550$@duckware.com> <000901cfc2c2$c21ae460$4650ad20$@duckware.com> <4A89264B-36C5-4D1F-9E5E-33F2B42C364E@gmail.com> <002201cfc2e4$565c1100$03143300$@duckware.com> <001e01cfc394$93ca5280$bb5ef780$@duckware.com> In-Reply-To: Date: Fri, 29 Aug 2014 12:54:13 -0400 Message-ID: <001001cfc3a9$ded8e740$9c8ab5c0$@duckware.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0011_01CFC388.57C74740" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQFFVy+FAO2HJAXNGbNNrLY/R/b/6gGg5QYjATtzUJsCM/8plgJDZN5dAwhNtMwCUyYrSQEMLbi7AlMWk0qcfDDF8A== Content-Language: en-us X-Provags-ID: V02:K0:ozeFII3c9uHzQgrcWFSzHJjBwtbPn55riLQ3x8GME5b jWKVcoKfX+FqJszfM5w50twgrOurorlDiYoCr37OM11dHGbq+Z yQ3sg4a69mm52kHEjhmUFTHjV9jK9BZkn3VtPd8ayeoLrqQueU VLqJirtuWTdDD8rIAr5Q11uMvc+w6Q+X60nYzV9ggomZSzQOWB EHv1Q4Kny4X6/lEy2W6/L89tF581wL1VJeEOg+x9UH5EGGaHHN byS6n7OKwaZuWm2jjc1NjsxjQu8wYvmQ4TsMc0rkz9gldpce3U DPOcjJMdLaiSpM01+z5yf8Q+oU5wn6a6sVoIxKBlltGCOLjQs4 jjThhZS5rsjKQUH7mUMWiiwUOUmxzk6r2w2mrSM4X X-UI-Out-Filterresults: notjunk:1; Cc: bloat@lists.bufferbloat.net Subject: Re: [Bloat] The Dark Problem with AQM in the Internet? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2014 16:54:13 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0011_01CFC388.57C74740 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable The additive increase is there in the raw data. =20 From: Jonathan Morton [mailto:chromatix99@gmail.com]=20 Sent: Friday, August 29, 2014 12:31 PM To: Jerry Jongerius Cc: bloat Subject: RE: [Bloat] The Dark Problem with AQM in the Internet? =20 > A =E2=80=98boost=E2=80=99 has never been seen. Bandwidth graphs where = there is no packet loss look like: That's very odd, if true. Westwood+ should still be increasing the = congestion window additively after recovering, so even if it got the = bandwidth or latency estimates wrong, it should still recover full = performance. Not necessarily very quickly, but it should still be = visible on a timescale of several seconds. More likely is that you're conflating cause and effect. The packet is = only lost when the boost ends, so if for some reason the boost never = ends, the packet is never lost. - Jonathan Morton ------=_NextPart_000_0011_01CFC388.57C74740 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

The additive increase is there in the raw = data.

 

From:= = Jonathan Morton [mailto:chromatix99@gmail.com]
Sent: Friday, = August 29, 2014 12:31 PM
To: Jerry Jongerius
Cc: = bloat
Subject: RE: [Bloat] The Dark Problem with AQM in the = Internet?

 

> A =E2=80=98boost=E2=80=99 = has never been seen.  Bandwidth graphs where there is no packet = loss look like:

That's very odd, if true. Westwood+ = should still be increasing the congestion window additively after = recovering, so even if it got the bandwidth or latency estimates wrong, = it should still recover full performance. Not necessarily very quickly, = but it should still be visible on a timescale of several = seconds.

More likely is that you're conflating cause = and effect. The packet is only lost when the boost ends, so if for some = reason the boost never ends, the packet is never = lost.

- Jonathan = Morton

------=_NextPart_000_0011_01CFC388.57C74740--