revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: "SHARRAH, LOWELL E" <ls3129@att.com>
Cc: iPerf User Group <iperf-users@lists.sourceforge.net>,
	Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] [Iperf-users] iperf 2 responsiveness test in 2.1.8-rc, --bounceback option
Date: Tue, 16 Aug 2022 13:35:52 -0700	[thread overview]
Message-ID: <CAHb6Lvp=ij3vut4f3vAcRi2v=jFbZgOnZaMS2bi=2FSi-RB6LA@mail.gmail.com> (raw)
In-Reply-To: <DM6PR02MB49390874E7AE22FA99C78188C26B9@DM6PR02MB4939.namprd02.prod.outlook.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 6598 bytes --]

Both iperf2 and iperf3 are end to end tools so they're above the network
so-to-speak. If the iperf3 is working as shown, not sure I understand the
question.

I do think engineers testing networks have to look at both responsiveness
(speed) and throughput (capacity/time.)  We've done a lot of work in iperf
2 around responsiveness and latency. Probably a good idea to perform this
class of testing too.

Bob

On Tue, Aug 16, 2022 at 1:02 PM SHARRAH, LOWELL E <ls3129@att.com> wrote:

> Can anyone tell me if iperf3 is designed to be used with cellular
> technology and if so what command should I be running.  I’ve been running
> these two commands for ethernet and getting great results.
>
>
>
> *iperf3 -c xxx.xxx.xxx.xxx -i 2 -t 20 -w 230K -P 3 *
>
> *iperf3 -c xxx.xxx.xxx.xxx -i 2 -t 20 -w 230K -P 3 -R*
>
>
>
>
>
>
>
> *LOWELL E. SHARRAH*
>
> *Professional-Network Support*
>
> *Service Experience & Operations*
>
> *221 N Washington Sq. Lansing, MI 48933 *
>
> *O: (517) 281-1443*
>
> *ls3129@att.com <ls3129@att.com>*
>
>
>
>
>
> Confidential
> This e-mail and any files transmitted with it are the property of AT&T
> and/or its affiliates, are confidential, and are intended solely for the
> use of the individual or entity to whom this e-mail is addressed. If you
> are not one of the named recipient (s) or otherwise have reason to believe
> that you have received this message in error, please notify the sender at
> 517-281-1443 and delete this message immediately from your computer. Any
> other use, retention, dissemination, forwarding, printing, or copying of
> this e-mail is strictly prohibited.
>
>
>
>
>
> *From:* Bob McMahon via Iperf-users <iperf-users@lists.sourceforge.net>
> *Sent:* Sunday, August 07, 2022 12:31 AM
> *To:* iPerf User Group <iperf-users@lists.sourceforge.net>
> *Cc:* Rpm <rpm@lists.bufferbloat.net>
> *Subject:* [Iperf-users] iperf 2 responsiveness test in 2.1.8-rc,
> --bounceback option
>
>
>
> Hi All,
>
> I've added a low impact, low duty cycle responsiveness test to iperf 2.  Man
> page is here. <https://iperf2.sourceforge.io/iperf-manpage.html>
>
> [rjmcmahon@bobcat iperf2-code]$ iperf -v
> iperf version 2.1.8-rc (6 August 2022) pthreads
>
> [rjmcmahon@bobcat iperf2-code]$ iperf -s --permit-key=mytest  -P 1
> --hide-ips
> ------------------------------------------------------------
> Server listening on TCP port 5001
> TCP window size:  128 KByte (default)
> Permit key is 'mytest' (timeout in 20.0 seconds)
> ------------------------------------------------------------
>
> [rjmcmahon@ryzen3950 iperf2-code]$ iperf -c hostname -i 1 --bounceback
> --permit-key=mytest --hide-ips
> ------------------------------------------------------------
> Client connecting to (**hidden**), TCP port 5001
> Bursting:  100 Byte writes 10 times every 1.00 second(s)
> Bounce-back test (size= 100 Byte) (server hold req=0 usecs)
> TCP window size: 16.0 KByte (default)
> ------------------------------------------------------------
> [mytest(1)] local *.*.*.96 port 38048 connected with *.*.*.123 port 5001
> (bb len/hold=100/0) (icwnd/mss/irtt=14/1448/15038)
> [ ID] Interval        Transfer    Bandwidth         BB
> cnt=avg/min/max/stdev         Rtry  Cwnd/RTT    RPS
> [mytest(1)] 0.00-1.00 sec  1.95 KBytes  16.0 Kbits/sec
>  10=11.333/9.247/15.596/2.493 ms    0   14K/11667 us    88 rps
> [mytest(1)] 1.00-2.00 sec  1.95 KBytes  16.0 Kbits/sec
>  10=10.164/9.340/13.791/1.417 ms    0   14K/10374 us    98 rps
> [mytest(1)] 2.00-3.00 sec  1.95 KBytes  16.0 Kbits/sec
>  10=11.301/9.321/14.310/2.010 ms    0   14K/10796 us    88 rps
> [mytest(1)] 3.00-4.00 sec  1.95 KBytes  16.0 Kbits/sec
>  10=11.242/9.432/14.401/2.128 ms    0   14K/10720 us    88 rps
> [mytest(1)] 4.00-5.00 sec  1.95 KBytes  16.0 Kbits/sec
>  10=11.576/9.558/14.442/2.196 ms    0   14K/10821 us    86 rps
> [mytest(1)] 5.00-6.00 sec  1.95 KBytes  16.0 Kbits/sec
>  10=11.310/9.514/14.615/2.151 ms    0   14K/10806 us    88 rps
> [mytest(1)] 6.00-7.00 sec  1.95 KBytes  16.0 Kbits/sec
>  10=10.944/9.310/14.490/2.233 ms    0   14K/10548 us    91 rps
> [mytest(1)] 7.00-8.00 sec  1.95 KBytes  16.0 Kbits/sec
>  10=11.584/9.468/19.286/3.254 ms    0   14K/10794 us    86 rps
> [mytest(1)] 8.00-9.00 sec  1.95 KBytes  16.0 Kbits/sec
>  10=10.987/9.378/14.322/2.139 ms    0   14K/10533 us    90 rps
> [mytest(1)] 9.00-10.00 sec  1.95 KBytes  16.0 Kbits/sec
>  10=11.449/9.930/14.722/2.151 ms    0   14K/10832 us    87 rps
> [mytest(1)] 0.00-10.03 sec  19.5 KBytes  15.9 Kbits/sec
>  100=11.189/9.247/19.286/2.190 ms    0   14K/11083 us    89 rps
> [  1] 0.00-10.03 sec BB8(f)-PDF:
> bin(w=100us):cnt(100)=93:1,94:9,95:5,96:11,97:9,98:2,99:5,100:6,101:9,102:3,103:3,104:1,105:1,106:2,107:1,115:1,129:1,130:1,132:1,137:1,138:2,139:3,141:4,142:2,143:4,144:3,145:4,147:2,148:1,156:1,193:1
> (5.00/95.00/99.7%=94/147/193,Outliers=0,obl/obu=0/0)
>
> Bob
>
>
> This electronic communication and the information and any files
> transmitted with it, or attached to it, are confidential and are intended
> solely for the use of the individual or entity to whom it is addressed and
> may contain information that is confidential, legally privileged, protected
> by privacy laws, or otherwise restricted from disclosure to anyone else. If
> you are not the intended recipient or the person responsible for delivering
> the e-mail to the intended recipient, you are hereby notified that any use,
> copying, distributing, dissemination, forwarding, printing, or copying of
> this e-mail is strictly prohibited. If you received this e-mail in error,
> please return the e-mail to the sender, delete it from your computer, and
> destroy any printed copy of it.
>

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #1.1.2: Type: text/html, Size: 9691 bytes --]

[-- Attachment #1.2: image001.jpg --]
[-- Type: image/jpeg, Size: 14958 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]

      reply	other threads:[~2022-08-16 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07  4:30 [Rpm] " Bob McMahon
2022-08-16 20:01 ` [Rpm] [Iperf-users] " SHARRAH, LOWELL E
2022-08-16 20:35   ` Bob McMahon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/rpm.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHb6Lvp=ij3vut4f3vAcRi2v=jFbZgOnZaMS2bi=2FSi-RB6LA@mail.gmail.com' \
    --to=bob.mcmahon@broadcom.com \
    --cc=iperf-users@lists.sourceforge.net \
    --cc=ls3129@att.com \
    --cc=rpm@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox