From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vsmta19-2.nsc.no (vip22scan.telenor.net [148.123.15.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 26AE93B29E for ; Fri, 5 May 2017 13:12:49 -0400 (EDT) Received: from [153.110.251.167] ([153.110.251.167:46322] helo=ilp-smtp01.man.cosng.net) by vsmta19-2.nsc.no (envelope-from ) (ecelerity 3.6.22.53981 r(Core:3.6.22.0)) with ESMTPS (cipher=DHE-RSA-AES256-GCM-SHA384) id FD/FA-18805-F82BC095; Fri, 05 May 2017 19:12:48 +0200 Received: from TNS-SKO-24-202.corp.telenor.no (TNS-SKO-24-202.corp.telenor.no [10.179.59.70]) by ilp-smtp01.man.cosng.net (Postfix) with ESMTP id CB8B1203F0; Fri, 5 May 2017 19:12:47 +0200 (CEST) Received: from TNS-SKO-24-212.corp.telenor.no (10.179.59.80) by TNS-SKO-24-202.corp.telenor.no (10.179.59.70) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 5 May 2017 19:12:47 +0200 Received: from TNS-SKO-24-208.corp.telenor.no (10.179.59.76) by TNS-SKO-24-212.corp.telenor.no (10.179.59.80) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 5 May 2017 19:12:47 +0200 Received: from TNS-SKO-24-208.corp.telenor.no ([fe80::b024:7a41:ba33:25b6]) by TNS-SKO-24-208.corp.telenor.no ([fe80::b024:7a41:ba33:25b6%12]) with mapi id 15.00.1178.000; Fri, 5 May 2017 19:12:47 +0200 From: To: CC: , Thread-Topic: [Cake] ER-X now running cake, thanks for the help. :) Thread-Index: AQHSxafcxON3arefFUmdI5Jip4yd/KHlzQRE///tWQCAADwttA== Date: Fri, 5 May 2017 17:12:46 +0000 Message-ID: <1494004366992.6614@telenor.com> References: <1493989225450.12354@telenor.com> <1493992526496.9641@telenor.com>,<87wp9vjtex.fsf@alrua-kau> <0F8A4A7F-2CD1-4DEF-99A9-1E14ECDA5D2D@telenor.com>, <661B553B-512D-4210-9CDF-0ADD1B21CE0C@toke.dk> In-Reply-To: <661B553B-512D-4210-9CDF-0ADD1B21CE0C@toke.dk> Accept-Language: nb-NO, en-US Content-Language: nb-NO X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.181.50.7] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SCAN_VERDICT: inbox Subject: Re: [Cake] ER-X now running cake, thanks for the help. :) 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: Fri, 05 May 2017 17:12:50 -0000 > Fra: Toke H=F8iland-J=F8rgensen =0A= >=0A= > Right, so you're measuring the actual latency experienced by the UDP pack= ets in the =0A= > unresponsive flow? Yeah, you'll get quite a bit of latency in that case. = But not sure that's a case =0A= > we should be optimising for...=0A= =0A= That was just the worst case scenario, not really meant to emulate user tra= ffic. And I'm not suggesting that the schedulers should be optimized for t= hat. But we can agree that 20+ seconds of delay is a bit much no matter how= it is measured? :)=0A= =0A= I also use nuttcp to model other kinds of traffic, such as VIOP, Voice over= WiFi, dumb udp vod that Telenor uses. Then I subject the router to variou= s kinds of line saturation and stress. Cloud upload, torrent, virus emulat= ion (zmap not really designed for that, but man, if you want to inflict pai= n on a router... zmap is your daddy). And we try to make sure that long li= ving tcp/vpn sessions are not torn down due to need for more sessions in na= t for yet another torrent session. Different QoS/schedulers behave differe= nt and we try and use the best possible solution for a given HW/access tech= . What works very well for balancing cloud upload and interactive traffic = like ssh or http may fail miserably on torrent. And the other way around. = On our legacy stuff we can't implement fq_codel, cake or sfq even. =0A= =0A= And as you know I also incorporate flent. =0A= =0A= =0A= -Erik=