revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] iperf 2 support for RPM and simple working loads
Date: Tue, 14 Jun 2022 19:53:40 -0700	[thread overview]
Message-ID: <CAHb6LvpiPMg3XDxVNnbeN26-QSbM860fgZOan4LuGSc7Q+kPBQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw71UesrTthYP5ZzPFtLDo4wHTSvPSEVBVvgTtR_PFac1g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2421 bytes --]

Cool, I'll add symbolic names per the code sample. Use -fb for formatting
without rounding or human units.  Otherwise it defaults to adaptive units
for human readability.

Bob

On Tue, Jun 14, 2022, 7:41 PM Dave Taht <dave.taht@gmail.com> wrote:

> I confirm the -t bug is fixed.
>
> It's also terrible of me to request, but symbolic names help. (is this
> shifted left 2?) There's a dscp to value lookup table I put into
> netperf years ago here, you can just rip:
> https://github.com/HewlettPackard/netperf/blob/master/src/dscp.c#L110
>
> this is a both test over tethered lte.  Are you rounding off stuff tho?
>
> [  1] 24.00-25.00 sec   400 Bytes  3.20 Kbits/sec
> 2=517.921/474.127/561.714/61.933 ms    0   13K/369863 us    120 rpm
> [ *2] 25.00-26.00 sec  3.41 MBytes  28.6 Mbits/sec
> [  2] 25.00-26.00 sec   126 KBytes  1.03 Mbits/sec
> [  1] 25.00-26.00 sec   200 Bytes  1.60 Kbits/sec
> 1=491.142/0.000/0.000/0.000 ms    1   13K/385380 us    60 rpm
> [ *2] 26.00-27.00 sec  3.14 MBytes  26.4 Mbits/sec
> [  2] 26.00-27.00 sec   189 KBytes  1.55 Mbits/sec
> [  1] 26.00-27.00 sec   200 Bytes  1.60 Kbits/sec
> 1=1484.553/0.000/0.000/0.000 ms    0    9K/406177 us    60 rpm
> [ *2] 27.00-28.00 sec  1.03 MBytes  8.61 Mbits/sec
> [  2] 27.00-28.00 sec  16.0 Bytes   128 bits/sec
> [  1] 27.00-28.00 sec   200 Bytes  1.60 Kbits/sec
> 1=552.013/0.000/0.000/0.000 ms    1    9K/496780 us    60 rpm
> [ *2] 28.00-29.00 sec  1.18 MBytes  9.88 Mbits/sec
> [  2] 28.00-29.00 sec   126 KBytes  1.04 Mbits/sec
> [  1] 28.00-29.00 sec   400 Bytes  3.20 Kbits/sec
> 2=771.394/411.026/1131.763/509.638 ms    0    9K/511648 us    120 rpm
>

-- 
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.2: Type: text/html, Size: 3095 bytes --]

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

      reply	other threads:[~2022-06-15  2:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 22:18 Bob McMahon
2022-06-13 23:43 ` Dave Taht
2022-06-14  0:02   ` Dave Taht
2022-06-15  1:42     ` Bob McMahon
2022-06-15  2:41       ` Dave Taht
2022-06-15  2:53         ` 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=CAHb6LvpiPMg3XDxVNnbeN26-QSbM860fgZOan4LuGSc7Q+kPBQ@mail.gmail.com \
    --to=bob.mcmahon@broadcom.com \
    --cc=dave.taht@gmail.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