From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (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 E9F7B21F2EC for ; Sat, 2 May 2015 09:25:56 -0700 (PDT) Received: by oign205 with SMTP id n205so87630221oig.2 for ; Sat, 02 May 2015 09:25:36 -0700 (PDT) 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=v10ISZ2emgmIV6d8YZ/lCrNSBfsV8oh+yBZJvH5QN3c=; b=ny+7ANtgYjJbPFmE7P0zl9P7pKRuZlbO7yZrJHIrlLe+CdIBf99cVGlORtPY9vCVlD 1VSfgbNjK2/c5zOr62YlmkH/+DfPzyI2voD4UHwYmTTfKMQ0iYll2wtTeC15SkikPVbd K9UYwDIWTjb6bXzqugWsnMR41algUS/qhGCF+JuZFFkPxprZGZjqEfA6mc9mrQPZc2Ng r/b5x/9UKFuAemQ/zqpLZuVsDOb2xBC6n3BfUK0z3yY19pXtKJRj4Ge8Ckk3PqajhsLl 7qBRJW++6HCsKjMeMhe5hddMe9muu6uq+1eRD2bawAtoNBAYNQ1rMG910tTnwskucg8i 18/Q== MIME-Version: 1.0 X-Received: by 10.60.103.36 with SMTP id ft4mr12060504oeb.39.1430583936729; Sat, 02 May 2015 09:25:36 -0700 (PDT) Received: by 10.202.71.139 with HTTP; Sat, 2 May 2015 09:25:36 -0700 (PDT) Date: Sat, 2 May 2015 09:25:36 -0700 Message-ID: From: Dave Taht To: Justin Beech , bloat Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Bloat] dslreports ping every second? 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: Sat, 02 May 2015 16:26:33 -0000 In one of the threads I saw that the dslreports test is one http ping every second. I am not really sure how that is handled - if the connection is tcp (?) and persistent, that measures 1 packet RTT, if it is a new connection, it is quite a few RTTs. And it is really not enough pings for valid statistical sampling. IF tcp, It would be vastly better to attempt a tcp ping every 10ms on an established connection (or whatever can be achieved, with 20ms being a good interval for most voip, 100ms seems easily doable, but...). This would accomplish two things: 1) A single packet loss would not cause a RTO (usually 250ms) but be flushed out (resent) on the next packet sent. So you would see replies get bunched in relation to loss and delay. 2) More pings more accurately track actual latency over a much tighter interval in general, particularly during the slow start phases at the beginning of the test where things tend to get really out of hand when you fire up tons of flows. In terms of plotting, I am quite fond of smokeping's methods, so you could still show the bar chart on a per second basis, but colored as per smokeping. (It had been my hope to one day leverage the webrtc apis to be able to test udp.) On what interval is it feasible to fire off a new http ping, and can the difference between a persistent connection and a new one be determined from within the browser? --=20 Dave T=C3=A4ht Open Networking needs **Open Source Hardware** https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67