From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id ECA2221F3B4 for ; Fri, 24 Apr 2015 02:02:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk Received: by alrua-kau.kau.toke.dk (Postfix, from userid 1000) id 0930FC40255; Fri, 24 Apr 2015 11:02:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toke.dk; s=201310; t=1429866152; bh=v7ZCGlwHzXV57Luh4hF/1CKdUGalJMXEAVU7NhtA1ys=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=A/QO4/JhNMRwjO7KO1ZIQWZJFFUCKFpYQOPosbOfxwLi3QVchSGf9MXN+jCjEwQFF XW/KO/iF8zW5rRfqUbCLdIbFvcUcW3PH/s7DVQVfNS3xKS5yr6ql0/WS8uv3JqsV7z ZJpz3XN1YzbkR5fjfdZcnYGDeBOs2DkKPHxPElrk= From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Sebastian Moeller References: <14cd9e74e48.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net> <20150422040453.GB36239@sesse.net> <1429676935.18561.42.camel@edumazet-glaptop2.roam.corp.google.com> <12383_1429692679_55376107_12383_9099_1_p7gmr0psut68sen0sao8o4lp.1429692550899@email.android.com> <1429710657.18561.68.camel@edumazet-glaptop2.roam.corp.google.com> <25065_1429716388_5537BDA4_25065_2328_1_63pyislbvtjf653k3qt8gw2c.1429715929544@email.android.com> <1429717468.18561.90.camel@edumazet-glaptop2.roam.corp.google.com> <5537CDB7.60301@orange.com> <1429722979.18561.112.camel@edumazet-glaptop2.roam.corp.google.com> <5537DA20.1090008@orange.com> <5537DE4D.8090100@orange.com> <1429771718.22254.32.camel@edumazet-glaptop2.roam.corp.google.com> <6C0D04CF-53AA-4D18-A4E4-B746AF6487C7@gmx.de> <87wq123p5r.fsf@toke.dk> <2288B614-B415-4017-A842-76E8F5DFDE4C@gmx.de> Date: Fri, 24 Apr 2015 11:02:31 +0200 In-Reply-To: <2288B614-B415-4017-A842-76E8F5DFDE4C@gmx.de> (Sebastian Moeller's message of "Fri, 24 Apr 2015 10:55:11 +0200") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87sibp526w.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Cc: bloat Subject: Re: [Bloat] DSLReports Speed Test has latency measurement built-in X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2015 09:03:09 -0000 Sebastian Moeller writes: > Oh, I can get behind that easily, I just thought basing the > limits on externally relevant total latency thresholds would directly > tell the user which applications might run well on his link. Sure this > means that people on a satellite link most likely will miss out the > acceptable voip threshold by their base-latency alone, but guess what > telephony via satellite leaves something to be desired. That said if > the alternative is no telephony I would take 1 second one-way delay > any day ;). Well I agree that this is relevant information in relation to the total link latency. But keeping the issues separate has value, I think, because you can potentially fix your bufferbloat, but increasing the speed of light to get better base latency on your satellite link is probably out of scope for now (or at least for a couple of hundred more years: http://theinfosphere.org/Speed_of_light). > What I liked about fixed thresholds is that the test would give > a good indication what kind of uses are going to work well on the link > under load, given that during load both base and induced latency come > into play. I agree that 300ms as first threshold is rather unambiguous > though (and I am certain that remote X11 will require a massively > lower RTT unless one likes to think of remote desktop as an oil tanker > simulator ;) ) Oh, I'm all for fixed thresholds! As I said, the goal should be (close to) zero added latency... > Okay so this would turn into: > > base latency to base latency + 30 ms: green > base latency + 31 ms to base latency + 100 ms: yellow > base latency + 101 ms to base latency + 200 ms: orange? > base latency + 201 ms to base latency + 500 ms: red > base latency + 501 ms to base latency + 1000 ms: fire > base latency + 1001 ms to infinity: fire & brimstone > > correct? Yup, something like that :) -Toke