From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mario.hock@kit.edu>
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de
 [141.3.10.81])
 (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 9A0623B25E
 for <bloat@lists.bufferbloat.net>; Fri, 21 Oct 2016 04:33:01 -0400 (EDT)
Received: from i72t450mh.tm.uni-karlsruhe.de ([141.3.71.47])
 by iramx2.ira.uni-karlsruhe.de with esmtpsa port 587 
 iface 141.3.10.81 id 1bxVFy-0007Kh-Sy
 for <bloat@lists.bufferbloat.net>; Fri, 21 Oct 2016 10:32:50 +0200
To: bloat@lists.bufferbloat.net
References: <CAGwEnGxMt3XUpqUxk80Pdqkd1pfX42BMc3AQ1zXsSGUAZjmkJQ@mail.gmail.com>
From: Mario Hock <mario.hock@kit.edu>
Message-ID: <78a109c2-421d-a55e-c996-bd3116f7e224@kit.edu>
Date: Fri, 21 Oct 2016 10:32:40 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <CAGwEnGxMt3XUpqUxk80Pdqkd1pfX42BMc3AQ1zXsSGUAZjmkJQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de  esmtpsa 1477038770.
Subject: Re: [Bloat] Large decrease in speed needed to combat bufferbloat?
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
 <mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
 <mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Fri, 21 Oct 2016 08:33:01 -0000

Hi,

Am 17.08.2016 um 10:21 schrieb Alec Robertson:
> The other question I would like to ask is, what's the absolute best way to
> see what the ping maximum actually is? With speedtest.net the ping only
> increases 1-2ms (pinging bbc.co.uk) and the same is true for dslreports.com
> (maybe a little bit higher, maximum of about 5ms) but on the dslreports.com
> site it says 9ms+ at times?

you can get access to the internal RTT estimation of the TCP stack with 
the tool TCPlog (https://git.scc.kit.edu/CPUnetLOG/TCPlog).

It shows (among other values): minRtt, maxRtt, avgRtt, meanRtt

But be aware that you have to run TCPlog on the sending end-system. 
Also, TCPlog is only available for Linux.

Best regards,

Mario Hock