[tsvwg] Re: [iccrg] iperf2 Android update: Bounceback fixes and IPv6 support
bob.mcmahon@umbernetworks.com Fri, 24 July 2026 19:54 UTC
Return-Path: <bob.mcmahon@umbernetworks.com>
X-Original-To: tsvwg@mail2.ietf.org
Delivered-To: tsvwg@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 408C111E64F82; Fri, 24 Jul 2026 12:54:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784922856; bh=AuV8qnMq6rPX3MP+Qs2YMAPVxJiW+4pkdqs+XqkjVEI=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=uPznRXffXfseBiaPx4I05BI/BfCZXYlMVbWG5BWYxjomLLg1dbHBPz7xIKGokN07M cWBNjWAiakAPw2ZgmZDc8p2tU/Nd9U+KTfZEpNXVU5p7Yp6Ro+6m0XEHNjM1x0zjmf W7jJra4YdGWLyMIhWPq5CQpkE4aMsUwzXIlNVaw8=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pQYLpcqc_qAE; Fri, 24 Jul 2026 12:54:15 -0700 (PDT)
Received: from mail.umbernetworks.com (mail.umbernetworks.com [198.74.51.139]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id AE79D11E64F73; Fri, 24 Jul 2026 12:54:15 -0700 (PDT)
Received: from webmail.umbernetworks.com (files.umbernetwork.com [198.74.51.139]) by mail.umbernetworks.com (Postfix) with ESMTPA id 04116213AA2; Fri, 24 Jul 2026 19:54:15 +0000 (UTC)
MIME-Version: 1.0
Date: Fri, 24 Jul 2026 12:54:14 -0700
From: bob.mcmahon@umbernetworks.com
To: Sebastian Moeller <moeller0=40gmx.de@dmarc.ietf.org>
In-Reply-To: <C038CFCD-48D7-40E5-8CCF-AAFD319DB54A@gmx.de>
References: <e90ff95915fe8fd5424eb851d1d8eb0a@umbernetworks.com> <0e2a00416528808b1570a4c729cb80cc@umbernetworks.com> <C038CFCD-48D7-40E5-8CCF-AAFD319DB54A@gmx.de>
Message-ID: <b4b7fd254cfd7071b7e7a320d778322b@umbernetworks.com>
X-Sender: bob.mcmahon@umbernetworks.com
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: OZEVQ2J7Y7YUYO5R4WOJHMMFVHBQIRAO
X-Message-ID-Hash: OZEVQ2J7Y7YUYO5R4WOJHMMFVHBQIRAO
X-MailFrom: bob.mcmahon@umbernetworks.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tsvwg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Tsvwg <tsvwg@ietf.org>, Hackathon <hackathon@ietf.org>, Ccwg <ccwg@ietf.org>, Ippm <ippm@ietf.org>, Iccrg <iccrg@irtf.org>, maprg@irtf.org, Koen DS <koen0607@gmail.com>, Chia-yu Chang <chia-yu.chang@nokia-bell-labs.com>, Frantisek Borsik <frantisek.borsik@gmail.com>, Andyhudson725 <andyhudson725@gmail.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [tsvwg] Re: [iccrg] iperf2 Android update: Bounceback fixes and IPv6 support
List-Id: Transport Area Working Group <tsvwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/rtbwDxa0B1TOmlRPiBAKPY63Jew>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Owner: <mailto:tsvwg-owner@ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Subscribe: <mailto:tsvwg-join@ietf.org>
List-Unsubscribe: <mailto:tsvwg-leave@ietf.org>
Thanks for the feedback Sebastian. It helps much. I'm adding some volatilty lines. The RSP moving average and smoothing is hiding that when it occurs. Also, looking into a stat like earth movers distance against a gausian. Or maybe against an golden run. https://en.wikipedia.org/wiki/Earth_mover%27s_distance We'll be recruting internal testers for Google Play soon. Bob > Hi Bob, > > this is getting better and better, CDF and PDF of the RPS data and > throughput traces of potential working loads are really helping > understanding what is going on! > > Regards > Sebastian > >> On Jul 24, 2026, at 08:38, >> bob.mcmahon=40umbernetworks.com@dmarc.ietf.org wrote: >> >> Hi All, >> >> I've updated the iperf 2 android bounceback test to display the >> histogram with a CDF overlay. UDP L4S bounce back is still beind coded >> up and tested. >> >> >> >> On 2026-07-22 11:57, bob.mcmahon@umbernetworks.com wrote: >>> Hi all, >>> An updated iperf2 Android build is available with two Bounceback >>> fixes. >>> First, a bug that caused responsiveness and RPS tests under working >>> load to fail after a few seconds has been fixed. The update has been >>> verified with a 50-second Bounceback run under load. >>> Second, the selected congestion-control algorithm now applies at both >>> ends of the Bounceback connection. Anyone comparing >>> congestion-control algorithms should repeat those tests with this >>> build. >>> The public responde.* servers support Reno, Cubic, and BBR, with >>> Cubic as the default. They do not currently support Prague. Prague >>> testing requires both a server and a device with Prague available. >>> The public servers have already been updated. If you use your own >>> iperf2 server, please update it from the 2-2-2 branch. >>> The public servers limit tests to 60 seconds, so please select a >>> shorter duration. >>> Android client presentation: >>> https://www.umbernetworks.com/IPPM_iperf2_Android_Pres.html >>> Install the updated APK >>> Download this exact file from the SourceForge file listing: >>> iperf2.2.2_21.bb_cca_fix.July2026_android.apk >>> https://sourceforge.net/projects/iperf2/files/ >>> Please select the filename directly rather than using the green >>> Download button, which may retrieve a different file. The APK can be >>> installed over an existing version. >>> Features worth testing >>> Bounceback now displays the minimum RTT reported by the kernel's TCP >>> statistics, together with a theoretical RPS ceiling: >>> Theoretical RPS ceiling = 1,000 ms / minimum TCP RTT >>> For example, a minimum TCP RTT of 20 ms gives a theoretical ceiling >>> of 50 request-and-reply cycles per second. >>> Minimum RTT is a TCP statistic, while observed RPS is measured from >>> the application-level Bounceback exchanges. Because each request >>> waits for its reply before the next request is sent, actual RPS will >>> normally be lower because of application processing, scheduling, >>> working load, and other path effects. >>> The public responde.* servers in Fremont, Vienna, and Newark also >>> support IPv6. The app can select IPv6 normally through the Host >>> field, or you can enable Force IPv6 (-V) to test the IPv6 path >>> explicitly. Your local network must also support IPv6. >>> Thanks again to everyone testing the app and providing feedback. It >>> is very helpful. >>> Bob >> >> _______________________________________________ >> iccrg mailing list -- iccrg@irtf.org >> To unsubscribe send an email to iccrg-leave@irtf.org
- [tsvwg] iperf2 Android update: Bounceback fixes a… bob.mcmahon
- [tsvwg] Re: iperf2 Android update: Bounceback fix… bob.mcmahon
- [tsvwg] Re: [iccrg] iperf2 Android update: Bounce… Sebastian Moeller
- [tsvwg] Re: [iccrg] iperf2 Android update: Bounce… bob.mcmahon
- [tsvwg] iperf2 Android testers needed - Google Pl… bob.mcmahon