From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 1B60E3B29E; Fri, 6 Sep 2019 04:27:03 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1567758422; bh=0JcKU3HNZNuukQ6tKujdxjiGjHna1P/J3NQz/49k+60=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=mCNIi40s2DyRoXTmNIwtVRHHmZDQ7jt1si2Os71B4DYWiA28WcRTR/rk5seOHJFw5 N41MBC70ESgnnfjJTZOpW0x16pqOXkXwMAAHTmKotrpOA8xqo0+zsUMqkHU7KRQ1FN 9rcAfpamGzSiVTzT/F4sq27WPP6bYjXF63/oSXLPNNMR64dbvLeyOhRAO7K1sLDXI+ HvSDVv+zi8R5EehUFZ3uoOPnOQR7Yk4m8VsGaiT09Csu+ZxiZQjLsMiwRnb6Z7VtQV bzVW6GmFrMlRoSX1+VLdM/6R+3bPufPRlE1YKsWzy5vEq4puI5lfbk1rFJtoG/uwtf lIyYkWIqPsXjQ== To: Mikael Abrahamsson , Matt Taggart Cc: cerowrt-devel , bloat@lists.bufferbloat.net In-Reply-To: References: Date: Fri, 06 Sep 2019 10:27:01 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <874l1p25ka.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cerowrt-devel] [Bloat] Ubiquiti Launches a Speed Test Network X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2019 08:27:03 -0000 Mikael Abrahamsson writes: > On Wed, 4 Sep 2019, Matt Taggart wrote: > >> So an interesting idea but they have some things they could improve. > > I've been considering what one should run in parallel with the speed test > to get an impression if the speedtest impacts performance of other flows / > realtime flows, similar to what dslreports speedtest does. > > I've considered running one or several simulated voip calls (50pps) and > record RTT, PDV, packet loss etc for this session. > > It would be interesting to hear any suggestions people have for a fairly > simple codebase that does this that can be included in these kinds of test > clients (both server and client end, and of course one that protects > against reflection attacks etc). > > iperf3 can be used for this, but from what I can see the iperf3 server > code isn't very friendly to multiple parallel tests or even resilient > against hung clients that doesn't close the test nicely. > > I also considered using WebRTC or VoIP libraries, does anyone know what > RTT/PDV/packet loss data can be extracted from some common ones? Pete coded up this wonderful tool for UDP-based latency testing; it's even supported in Flent, and available on some (all?) the public-facing servers: https://github.com/heistp/irtt -Toke