From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 452943CB35 for ; Tue, 11 Sep 2018 04:43:20 -0400 (EDT) Received: from [172.16.11.53] ([134.76.241.253]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LoVBq-1fNalI0n3S-00gVbv; Tue, 11 Sep 2018 10:43:18 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Sebastian Moeller In-Reply-To: Date: Tue, 11 Sep 2018 10:43:17 +0200 Cc: Pete Heist , Cake List Content-Transfer-Encoding: quoted-printable Message-Id: <3E4C6925-5E21-4BCB-BAAE-015EB8AEC3E1@gmx.de> References: <87zhwxzh8o.fsf@toke.dk> <139B295B-7371-43DE-B472-DE629C9B8432@heistp.net> <87efe65wol.fsf@toke.dk> <6C556301-015B-4903-AE5A-F22D3517FFCC@heistp.net> <79F47FB1-6B00-4753-930B-950FB8CD3850@gmx.de> To: =?utf-8?Q?Dave_T=C3=A4ht?= X-Mailer: Apple Mail (2.3445.9.1) X-Provags-ID: V03:K1:ySdSBA32ksGIGtcj524PkRZFORn6PUBNQRhyH6Tq5nPCx3uK7cQ LRC5vbPloa01QJhVy9xIDjrLRJ6eoUScERJlvkpYgtzs4fUTIMS8uoEIwuObIAFmxe5yLE2 Ks7NgTWR3BuWVhkQLfNWgQDChxlw87l6BjaUvJwtZhlP+UiwC4uF0qYzoPNEW5u3wNT5R8c qFP5MaXJDvbiEAQ15EU/Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:DXPM8Q/Im2Y=:nnqJF2stOBTXQ1ACvdfyp1 TrQe8kijLKcxH0X+qYHsTmPlV3aCmvggfxVg5VucIzLVpageu/QpWDKyCng0rJsv2iNJuz0om 36RMuy+/GB7L9Ivw4+MMH3lvn1iv/0D4UIdRAcPUE9O4yzyy5HVX2E46jkP/Y4Bm7Z2eWcdv5 rW6zvIjGIQ/HGA62ZmKrS4eKaWTREaKMEEVO/+pKx5B85pvxPAx4gg6N6GdJKExnoCaQfCi+I 3+Vh7M713C/nGoEp2jhDwK36rRc14fGTGmNIr02ITLeSIDpAFt6fgoag++cpTZRL/lo++ku7y g+iuvHfo5pERrmDACxLKpFvtphL18kx0++87yJ1IMLpjM6Ecp/DN0fl8AYWQnN19xujogYsdq Gi8+V4NIcNkcm3c3ITv5xniZKxl9orarNNIeQUb2G/e22mD6pBZVd7b0RJ+jNjJDcmBQ0+DTy +hFhphABTWfCdOljdl75QglrhRFpGyrXVbwPJC6mk8JBdGCghiPiEOUrho5gltjKsl7l51Xco vDGio9vKrRVxSSCMPlVGoyXoVriuQJ+DDRdt4Ne3Zd7qVdiZRbVfcB+y1qIy4p7zduzhS2Kpb fEjEz6RvAnVgX/PK5OcdN+kHGYbsw+19yEZL1sfYx/0wd7fTzuVIM9ngE6rmZjCDpNnEtKSwx FF2okMvXzRqgXkjl8o6pGg///mPiEIVmG60aU8IesGx0qiN8CQjMnDwZbTOIDgkedzcGg1aTd mfA7b35LYdoy7lhq+WQ28YmDfAr/k/4SNYjumQZAS4Ad82U1bSJIZNj8AtFPAFxTssKk+sdo7 +1moic3 Subject: Re: [Cake] Cake vs fq_codel and c/burst on an ER-X bridge 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: Tue, 11 Sep 2018 08:43:20 -0000 Hi Dave, > On Sep 11, 2018, at 10:30, Dave Taht wrote: >=20 > On Tue, Sep 11, 2018 at 1:20 AM Sebastian Moeller = wrote: >>=20 >> Hi Dave, >>=20 >>> On Sep 11, 2018, at 10:20, Dave Taht wrote: >>>=20 >>> What I "fixed" was on the apu2 with the burst/cburst change, I went >>> from completely bottlenecked on one softirq to having 3 eat cpu, and >>> from 400mbps to 900mbps. Now, that's a quad core and the e1000 (?) >>> driver. The edgerouter X is a dual core, and you did see a small >>> improvement in throughput, but I'd hoped for more. >>=20 >> Well, assuming my intuitions about how burst/cburst ameliorate the = issue, we might simply have to say accept an additional 5ms delay/jitter = to make it perform better. It is basically the same batching approach = that always helps throughput of a cyclic process can not be repeated = often enough, simply do more per iteration... >>=20 >> Best Regards >> Sebastian >>=20 >=20 > I buy what you are saying. I just wished it was a magic bullet for > other than the apu2! I guess I will have a look at exposing burst in the gui/config file to = allow easier testing. (I aim for defaulting to the automatic mode we = currently use, but will also look at potentially changing the = calculations). I wonder to what degree htb's quantum is at play again after that. If I = understand correctly quantum defines the granularity of dequeuing the = different priority tiers, so the higher quantum the higher the = choppyness/lumpiness of packets of different tiers, no? If this is true, = shouldn't quantum also be defined in milliseconds instead of size, so = that we have a better handle on the potential latency cost of doing so? Best Regards Sebastian > --=20 >=20 > Dave T=C3=A4ht > CEO, TekLibre, LLC > http://www.teklibre.com > Tel: 1-669-226-2619