[iccrg] iperf2 Android client (alpha) — feedback w anted
[email protected] Mon, 20 Jul 2026 18:08:02 -0700
| Newsgroups | gmane.ietf.irtf.iccrg,gmane.ietf.tsvwg |
|---|---|
| Message-ID | <[email protected]> |
--===============2774753916328622672== Content-Type: multipart/alternative; boundary="=_8a44e86a401d7744c129a481660c23f7" --=_8a44e86a401d7744c129a481660c23f7 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Hi all, Unfortunately, I am unable to attend IETF 126, but I wanted to share some work that may be of interest. I have built an Android client for iperf2 that supports TCP, responsiveness, and L4S testing directly from a phone. The core functionality is working, and I would appreciate feedback on the user interface and reported statistics before beginning the public-release testing cycle. The app supports: * TCP: Throughput, RTT, congestion window, inflight and unsent data, and selectable congestion control. * Bounceback: Round-trip responsiveness while upload and download traffic are running concurrently. * UDP L4S: CE marking, marking probability, loss probability, congestion window, inflight data, and estimated queued data. Each metric is displayed as a live dial paired with a time-series sparkline so changes across metrics can be correlated during a test. A walkthrough of the modes and meters is available at: https://iperf2.fi-wi.com [1] Download the Android APK from: https://sourceforge.net/projects/iperf2/files/ Look for the iperf2*_android.apk file rather than using the large green Download button, which may select a different file. I would particularly value feedback on: * Whether each test mode is understandable * Whether the dials and sparklines are clear and useful * Whether the reported statistics make sense * Any metrics that seem confusing, missing, or unnecessary This is alpha software, so there are still rough edges, and the interface may change between builds. The public responde.* servers are not performant and stop tests after 60 seconds of traffic. They are provided only for user-interface verification--connecting, authenticating, running a test, and rendering the live meters. Do not treat results from those servers as meaningful measurements of your network path. For performance testing, point the app at your own iperf2 server. The app uses the iperf2 2.2.2 release binary available on SourceForge from the 2-2-2 branch. Please reply directly to me or send feedback to [email protected]. Thanks, Bob Links: ------ [1] https://iperf2.fi-wi.com/ --=_8a44e86a401d7744c129a481660c23f7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset= =3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen= eva,sans-serif'> <p>Hi all,</p> <p>Unfortunately, I am unable to attend IETF 126, but I wanted to share som= e work that may be of interest.</p> <p>I have built an Android client for iperf2 that supports TCP, responsiven= ess, and L4S testing directly from a phone. The core functionality is worki= ng, and I would appreciate feedback on the user interface and reported stat= istics before beginning the public-release testing cycle.</p> <p>The app supports:</p> <ul> <li> <p><strong>TCP:</strong> Throughput, RTT, congestion window, inflight and u= nsent data, and selectable congestion control.</p> </li> <li> <p><strong>Bounceback:</strong> Round-trip responsiveness while upload and = download traffic are running concurrently.</p> </li> <li> <p><strong>UDP L4S:</strong> CE marking, marking probability, loss probabil= ity, congestion window, inflight data, and estimated queued data.</p> </li> </ul> <p>Each metric is displayed as a live dial paired with a time-series sparkl= ine so changes across metrics can be correlated during a test.</p> <p>A walkthrough of the modes and meters is available at:</p> <p><a href=3D"https://iperf2.fi-wi.com/">https://iperf2.fi-wi.com</a></p> <p>Download the Android APK from:</p> <p><a href=3D"https://sourceforge.net/projects/iperf2/files/">https://sourc= eforge.net/projects/iperf2/files/</a></p> <p>Look for the <code>iperf2*_android.apk</code> file rather than using the= large green <strong>Download</strong> button, which may select a different= file.</p> <p>I would particularly value feedback on:</p> <ul> <li> <p>Whether each test mode is understandable</p> </li> <li> <p>Whether the dials and sparklines are clear and useful</p> </li> <li> <p>Whether the reported statistics make sense</p> </li> <li> <p>Any metrics that seem confusing, missing, or unnecessary</p> </li> </ul> <p>This is alpha software, so there are still rough edges, and the interfac= e may change between builds.</p> <p>The public <code>responde.*</code> servers are not performant and stop t= ests after 60 seconds of traffic. They are provided only for user-interface= verification—connecting, authenticating, running a test, and renderi= ng the live meters. Do not treat results from those servers as meaningful m= easurements of your network path. For performance testing, point the app at= your own iperf2 server.</p> <p>The app uses the iperf2 2.2.2 release binary available on SourceForge fr= om the <code>2-2-2</code> branch.</p> <p>Please reply directly to me or send feedback to <a href=3D"mailto:feedba= [email protected]">[email protected]</a>.</p> <p>Thanks,</p> <p>Bob</p> </body></html> --=_8a44e86a401d7744c129a481660c23f7-- --===============2774753916328622672== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaWNjcmcgbWFp bGluZyBsaXN0IC0tIGljY3JnQGlydGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg dG8gaWNjcmctbGVhdmVAaXJ0Zi5vcmcK --===============2774753916328622672==--