From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 6861A3B25D for ; Sun, 24 Jul 2016 13:21:26 -0400 (EDT) Received: from hms-beagle.speedport_w723_v_typ_a_1_01_016 ([93.237.73.111]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MDFB2-1bWobw2Fjg-00GXqz; Sun, 24 Jul 2016 19:21:24 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: moeller0 In-Reply-To: Date: Sun, 24 Jul 2016 19:21:23 +0200 Cc: Jonathan Morton , cake@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: <001B301F-5F3D-4751-A252-ED67021B0BC2@gmx.de> References: <66C89432-6E70-422F-A638-7522BF233707@gmail.com> <35967373-D9F6-4C0C-8005-787DB8C7B1BB@gmx.de> <7ECE7E7A-0310-4DC4-8AC9-29B0F1F2E383@gmx.de> <4F22259A-17C8-4353-B34B-55D7E194D1EB@gmx.de> <43469614-F02B-4D9B-8D0E-14D0F4211CF1@gmail.com> <0B5FF17F-817F-4993-826D-DE55387D8D91@gmx.de> To: Loganaden Velvindron X-Mailer: Apple Mail (2.2104) X-Provags-ID: V03:K0:OtNUAvFLB5c3ewK7KMX9wqVr4C//wOH/HiMzm4z8M28sivxcY0V tUNJPbmcPscFUl+KJ6B/gCOPQWDITlv+VjB8N1zQitjel3uEVBxq2g9I13BqnCfEjP9uaqp 8/nMU+T0JHHdnK9MkV8Pqur0qxD4b7UylaxQw4REmHdr387iRQ3/xCxNxnSI88pqLyBS0oV nMpE4yc0A16YwgHfbeOnw== X-UI-Out-Filterresults: notjunk:1;V01:K0:Ar1ZchFD3xo=:r+08tcV3tLrhjmt5i0b4Xy IiQ26Q6WwqMKmktKnRJy5+raTS0G3ns2BEbn2yewNJSDSd8afWBnhe3p5YRoF/nyRibwXLaGU mdJUg2IHRlQYCG6Lm24Gkmfn5ij8yObAUKbnmCBEch2qEL4e30rh1fD+S0KKlFg4idFvwhDvE l1fM1/EpsqMNbKd69wdnGJllGDjtxErtLDhrxyJ7T8fiDGXEux97YiyeC+klpKPiPSyCifym7 aatkr7fJnl86QnVUNIq9I+akycX3AKYm9OzI4+TQBpIUGGXUuNSUc+kyKxGeLxjdMjl66AmQx 4HXm/HvvkKnQfHzjnGUsxbERS2ZcowTPS/bJ7KZ6wiHsraZfh/DpIY6tSQc6oz/DdVk2PFZ9L laZCr7tXkPZZtuvnkXieLRbf5kFFpnRKHmhIhpo0k3r3QEnFo3rGOVpDHbgCiUv3VXMXvv+f5 h7Dt5rSmQolY+kpuBZaEy+grCYLZ7B+9BDX2Qe5aDRvIZNdaSiWBW74t+2tcbZ0AQGywpYewh kLNbj1tt3gVhG+cf3gKlpG4Nz+PybAqOaMc32NnMLthYDZdvTIetpvgoxhwsOCtNtKDifikvr pFHQVktaxik1HhMG/FhOTn6wrS3UQVlC1aB/ci1WMeGrLpI3lJQffDuDfEn4Mjk4PsCgCwlqd nb6YR8KMO2UJLI+FCgh9OGwouqj9EuF6zIuCVfdmX+EqxTOUKC1QrkRdYbffItVSGkSqe1s8U g6LOvvkOPnMSb5rfptJtgSBiKF6PBrLDpXgjh0C7+q3cnmxiPROOXrAyEoU8Yv1QogTNSceD/ 8WduuX6 Subject: Re: [Cake] fq_codel on 3g network in Mauritius X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 17:21:26 -0000 Hi Loganaden, > On Jul 24, 2016, at 19:13 , Loganaden Velvindron = wrote: >=20 > On Sun, Jul 24, 2016 at 6:40 PM, moeller0 wrote: >> Hi Jonathan, >>=20 >>> On Jul 24, 2016, at 13:28 , Jonathan Morton = wrote: >>>=20 >>>=20 >>>> On 24 Jul, 2016, at 13:53, moeller0 wrote: >>>>=20 >>>> In theory interval can be different for ingress and egress (think = old-school SAT-internet with modem upload) it probably is easiest to = only configure one interval setting for the time being. >>>=20 >>> Since the interval parameter depends on the RTT, not the one-way = delay, it should always be the same both ways (except for = inter-packet-time effects). >>=20 >> Thanks for setting this straight. I was confused; the thing = that lingered at the back of my mind was that if we do the target = extension for one direction and correct the interval in that direction, = we should also correct the interval in the other direction, especially = since as Jonathan points out the interval describes the full = back-and-forth path=E2=80=A6 >>=20 >> Best Regards >> Sebastian >>=20 >=20 > I've updated the target to be 22ms based on my current interval of = 450ms. >=20 > http://www.dslreports.com/speedtest/4523668 >=20 > It's not pretty, but the quality is A or A+. >=20 > It's interesting to see the saw tooth pattern for the upload. This was > not the case when the target was 5ms, which I believe was calculated > based on a 100ms worse rtt. I just noticed you use the dslreports pre-canned profiles for measuring. = I would recommend against doing that. As these will use different number = of upstream/downstream flows per profile making comparisons between = different profiles harder. I would recommend to get a free dslreports = account and use the speed test configuration to use a fixed number of = flows per direction (I typically use 16/16, but on slower links often I = do not get all 16 going, in that case I retry with a lower number of = flows, also set manually). After registration you can also request high = resolution buffer bloat measurements, which nicely illustrate a link=E2=80= =99s behavior under load (but might not work well on very slow links, so = maybe you are already running the optimum configuration). Best Regards Sebastian