From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) by lists.bufferbloat.net (Postfix) with ESMTPS id F3AE83C9F2; Mon, 18 Jan 2016 05:51:33 -0500 (EST) Received: by mail-qg0-x233.google.com with SMTP id o11so553576199qge.2; Mon, 18 Jan 2016 02:51:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0Sf7K24JLvr19PaQrfbKo57jMeBYFe8eRzq6yJ3dgNY=; b=YvYDF6ENo5HEWokgngJktiKRFeUvYAthhdo2db/c24bAEq1iH4sVYOMVcvQMWEeBa5 0t0R2Sz7kLMFE0PpIpyc2NFy+vQ2CitXhH6YlKJQOqzGOAlHb1DEi08tXZEVAHWe6P1G bFlRafms0xGdlKTMZHtDyiJX4fM91ijCQ4dZkvnGxDht0asbky96dY0D2THeT8Cx+5zY jZWwbS19NaEH24AFamT8UXLP7WlBFiflmdzGINXkU3msnriE/7MQhiRB1dmOFV5TB5Gy Lalerm0HboPuqCsTO9wutVktoSL6FCKMg9bo066JDOeWjZB5ANXhUp7iu+NYbbIuixkG jXQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=0Sf7K24JLvr19PaQrfbKo57jMeBYFe8eRzq6yJ3dgNY=; b=ITXRe++tkPU/J/DhaJBdYaVjSxdrI72FQGAkUhof1Tdb54X7YVFONLH3lzHc1ttfiq zgukmt6QsEx7YYb5HMhsYzIYAT0MsvgKnXZnhxpfo9aFEcYZefufksZhXng/S4113LqZ 61aM5wvXx0yo9tY80E/MP/ARxvWbOS//fWVP0lKncgPyTlkTVjkeQ/CcKOY/lYgGR7cB tV4yKl0Td0ADGo0h4vMTe/K6bur/XjqFipW97FBPz2/Pz/LojohrcU1r7iNU6V6n2bE4 lJgLJshDjdB2J+i/2M7dNOTqf3OxRbgEDEL8iool/DUWPyk6Bx/FPqBDIi6P80C3QCoY SpSw== X-Gm-Message-State: ALoCoQnGLjzriM5vLIJSs2DoCZRBjXqwoqQGgHRAWQI0lQoWrlFq0AfSkhBZh1SVUF9cowwvDwiISCQN+fZ3xsFhU7gl8EBu0g== MIME-Version: 1.0 X-Received: by 10.140.97.5 with SMTP id l5mr30091179qge.84.1453114293001; Mon, 18 Jan 2016 02:51:33 -0800 (PST) Received: by 10.140.16.178 with HTTP; Mon, 18 Jan 2016 02:51:32 -0800 (PST) In-Reply-To: References: <6737994D-CE0B-46F5-B55C-A584FF6A8014@gmail.com> Date: Mon, 18 Jan 2016 10:51:32 +0000 Message-ID: From: Alan Jenkins To: Valent Turkovic Cc: Jonathan Morton , "cerowrt-devel@lists.bufferbloat.net" , make-wifi-fast@lists.bufferbloat.net Content-Type: text/plain; charset=UTF-8 Subject: Re: [Make-wifi-fast] [Cerowrt-devel] routers you can throw off the back of a truck X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2016 10:51:34 -0000 On 18/01/2016, Valent Turkovic wrote: > @everybody any ideas how to tweak current "simple.qos" and > "simplest.qos" scripts in OpenWrt for 3G and fiber optics? On fiber > optic connection idle latency is around 30ms and on 3G connection is > around 60ms, do I need to change 5ms default in fq_codel to these > values? How? Target should stay at 5ms, unless bandwidth is low ( < 2Mbit). qos-scripts will tweak it according to the bandwidth you set. Interval needs to match the expected round-trip-time, as a maximum across most endpoints. The 100ms default interval works well in many cases... a base of 60ms might argue to increase it slightly for 3G, if you expect some trans-continental destinations.[1] Source: an update from the original Codel author. Might not sound directly related to your question, but I guess 3G falls under their definition of a "bursty MAC". "Many experimenters believe the value of target needs to be increased independently of interval in this case. This note is to help explain why this is not so." http://pollere.net/Pdfdocs/noteburstymacs.pdf The problem is that you need either a fixed rate you can use, or an underlying connection that isn't itself horribly over-buffered. (Ethernet with BQL, or dialup modems in the era of wondershaper...) 3G doesn't guarantee either :(. I assume it also has the wireless problem, of retry-induced latency on poor signal. (ala Taht's "infinite retry" bug). If Johnathans new "autorate_ingress" solves or mitigates it for ingress, that would be miraculous. I had assumed it was most applicable to point-to-point links which change the bitrate they use over time due to changing signal quality, e.g. point-to-point wireless v.s. weather. (IIRC he had this clever idea of measuring the maximum bitrate of two packets received back-to-back). Btw make sure you've measured the idle latency during the busiest period for the 3G network (for which it is still usable). People observe high variations during the day. Regards Alan [1] E.g. from Europe you might expect some US endpoints, but not worry about performance degradation to Australian-only servers. You can try pinging the world from your browser with http://www.dslreports.com/tools/pingtest :).