From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nasse.dc.kau.se (smtp.kau.se [193.10.220.39]) (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 7733E3BA8E for ; Thu, 21 Sep 2017 06:58:41 -0400 (EDT) To: References: From: Stefan Alfredsson Message-ID: Date: Thu, 21 Sep 2017 12:58:39 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-ClientProxiedBy: Exch-A2.personal.kau (130.243.19.83) To Exch-A1.personal.kau (130.243.19.82) Subject: Re: [Bloat] different speeds on different ports? (benchmarking fun) X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2017 10:58:41 -0000 On 2017-08-30 07:15, Aaron Wood wrote: > > The current hypothesis that we have is that this is due to either > traffic class, or the ports that traffic are running on.  I've ruled > out the ping streams, as a parallel set of netperf tcp_maerts > downloads has the same 120Mbps roof. Also think of server differentiation (maybe full capacity to known measurement servers, shaped for other destinations). Does dslreports have flent/netperf responders on their servers as well? > > It would be interesting if we could run some netperf tests using port > 80/443 for the listening socket for the data connection (although if > doing deep-packet inspection, we might need to use an actual HTTP > transfer). UDP 443 (QUIC) would also be interesting for comparison. /Stefan