From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 5744821F725 for ; Tue, 1 Dec 2015 10:08:46 -0800 (PST) Received: by oixx65 with SMTP id x65so9011415oix.0 for ; Tue, 01 Dec 2015 10:08:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=22RYhdTtv6se8SJo7tOj2UVTghnVv7nhv8P+UsQi4Ao=; b=C+2ee8WIp648xetXe/pm4fvr9g4Z0haz3jIJxPyvYefsUu1SMu3N/qByBA5am9bVBQ xvlK2Rm5VuuIHfrxPo8zr+Wszd2iEyNPuhqsZ51XIqWPrj/XDe7X6nz234kfl9hAOdsI pmr/bZRgXCj3JfuPOZIKYxA3ZkQqEqh3n4rb+94E6UQj5LcF88FzNZWumL9S9gfMYA3B FlLuTHFJmIjdmrBEq2WPIE/wIt7u8wYMPEjWEoxvCGWX1wbULkonaVPuNxKCTsBMiF94 PHBXSzROmzdfn+XGVnmjVRWkF13Y7R65fpUTbI1FGq7M8zMb4GKmDvp/E6k+1O11/je1 b4pg== MIME-Version: 1.0 X-Received: by 10.202.64.198 with SMTP id n189mr48991445oia.139.1448993325971; Tue, 01 Dec 2015 10:08:45 -0800 (PST) Received: by 10.202.187.3 with HTTP; Tue, 1 Dec 2015 10:08:45 -0800 (PST) Date: Tue, 1 Dec 2015 19:08:45 +0100 Message-ID: From: Dave Taht To: "codel@lists.bufferbloat.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Codel] what RTT was fig 7 in the codel paper? X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2015 18:09:09 -0000 What RTT was fig 7 in the codel paper? (the one that showed codel's reaction to bandwidth changes?) http://queue.acm.org/detail.cfm?id=3D2209336 I am amusing myself by trying to create an automated string of flent tests to duplicate those results, now that flent has gained tools that can plot queue depth as well as ping, we have a testbed with fully controllable RTT, etc. http://snapon.cs.kau.se/~d/nichols/basiccodel.png "To roughly emulate a (nominal) 100-Mbps Wi-Fi link subject to degradation, we used a load of four FTPs and five Web connections per second and changed link rates at 50-second intervals (over the 300 simulated seconds), first dropping to 10 Mbps, then to 1 Mbps, then jumping to 50 Mbps, dropping to 1 Mbps, and finally jumping back to 100 Mbps. Buffer capacity is a single BDP (830 packets) for the nominal rate. This scenario was repeated for CoDel, Tail Drop, and RED. " -- Dave T=C3=A4ht Let's go make home routers and wifi faster! With better software! https://www.gofundme.com/savewifi