Re: [tsvwg] thoughts on operational queue settings (Re: CC/bleaching thoughts for draft-ietf-tsvwg-le-phb-04)

Mikael Abrahamsson <swmike@swm.pp.se> Sat, 14 April 2018 06:08 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13061127599 for <tsvwg@ietfa.amsl.com>; Fri, 13 Apr 2018 23:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9wsDeDKV4tp for <tsvwg@ietfa.amsl.com>; Fri, 13 Apr 2018 23:08:51 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3273A126C0F for <tsvwg@ietf.org>; Fri, 13 Apr 2018 23:08:51 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 15F4FAF; Sat, 14 Apr 2018 08:08:49 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1523686129; bh=lSpadTS61ZYkFUfLzR6cYG3N1V94zHwvjbhhWmXCcfE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=jGpjaxTTXvnwuc+3qcyTMO5SWmlDVeLgbES5FTsSMsAo9CDk32IEMwfGxsyjFnVFc /mtnD68LcBt2uGEXi5DVVaHOn/sLTTKCRERnpCPcdIKGXdR7i7Q5zqX6vBdzFgItsv fmbYou+wjSbeecFmYyU1c96D21GVFjE5wN13/bI8=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 0F7739F; Sat, 14 Apr 2018 08:08:49 +0200 (CEST)
Date: Sat, 14 Apr 2018 08:08:49 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Toerless Eckert <tte@cs.fau.de>
cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, tsvwg@ietf.org
In-Reply-To: <20180413172245.kkjxajwdlp2hifkd@faui48f.informatik.uni-erlangen.de>
Message-ID: <alpine.DEB.2.20.1804140757180.18650@uplift.swm.pp.se>
References: <20180406160344.xwfqgzhzfto56jhq@faui48f.informatik.uni-erlangen.de> <5252b232-13df-fb19-227f-95694572b86c@kit.edu> <20180412012544.tmnzec3zddlyrmlb@faui48f.informatik.uni-erlangen.de> <39fb9195-b46f-945f-d414-936f97a59d87@gmail.com> <alpine.DEB.2.20.1804120818210.18650@uplift.swm.pp.se> <20180412080515.g5qkjqmluru26nib@faui48f.informatik.uni-erlangen.de> <alpine.DEB.2.20.1804121007560.18650@uplift.swm.pp.se> <20180412091235.i3dj3j4ktvriq5fq@faui48f.informatik.uni-erlangen.de> <alpine.DEB.2.20.1804130612030.18650@uplift.swm.pp.se> <20180413172245.kkjxajwdlp2hifkd@faui48f.informatik.uni-erlangen.de>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/MIN6QS1w0PbgLPaeuJarQyoEGO4>
Subject: Re: [tsvwg] thoughts on operational queue settings (Re: CC/bleaching thoughts for draft-ietf-tsvwg-le-phb-04)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Apr 2018 06:08:53 -0000

On Fri, 13 Apr 2018, Toerless Eckert wrote:

> Q1: What would be the impact to BE traffic if one would scale BE 
> queue-size and AQM parameters to 1/20th of what they ideally should be ? 
> I guess some performance impact, but any useful estimate how big that 
> impact would be ? Worse than overall performance, would it create more 
> unfairness between short RTT and long RTT flows ? (i fear so).

In my testing with 10 TCP flows, 30ms RTT, hundreds of megabits/s of 
access speed configured, the 0.5ms LE buffer before drop probability went 
non-zero (5% LE 10ms configured, resulting as you say in 0.5ms actual when 
there is no competing BE) meant the LE traffic would not utilise the link 
speed but would sawtooth between 75%-95% of used capacity (1 second 
interval shown in iperf3).

> I would hope we can figure out a good recommendation for LE for the LE 
> B/20 queue config. If that setup will give reasonable performance with 
> existing TCP algorithms, e.g: in the absence of BE traffic LE with QUBIC 
> TCP could get to > 50% link, that would be a good start and keep LE 
> requirements reasonable (one more queue per link, 5% more bufferspace 
> need per link).

When I configured LE to insted have 50ms before RED curve (resulting in 
2.5ms when there is no other traffic) the above test fared a lot better. 
This however caused ~50ms of buffer bloat when there was competing BE 
traffic.

This is also heavily dependent on access speed, the red curves need to be 
different depending on if the access speed is 10 megabit/s, 100 or 1000. 
The lower the speed, the more ms you need in order for the flows to behave 
more smoothly.

> The less a problem it is, the easier we could skip the M/20 setup for LE 
> and would only need to worry about the bufferbloat questions for LE - 
> which should be much less of an issue. Just from the perspective of 
> evaluating the lowest feasible additionalr esource seetup for LE i would 
> still like to see if there are answers for the M/20 setup.

My results show decent performance even at very low queue depths for LE 
traffic, at least at higher access speeds.

My main interest in this anyway is to solve the problem with access speeds 
in the 10-1000 megabit/s range and come up with solutions that are 
deployable on most providers existing BNG (and equivalent) devices.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se