This is Rick Jones' feeble attempt at a Texinfo-based manual for the netperf benchmark.
Copyright © 2005-2007 Hewlett-Packard Company
Permission is granted to copy, distribute and/or modify this document per the terms of the netperf source licence, a copy of which can be found in the file COPYING of the basic netperf distribution.
--- The Detailed Node Listing ---
Introduction
Installing Netperf
The Design of Netperf
Global Command-line Options
Using Netperf to Measure Bulk Data Transfer
Options common to TCP UDP and SCTP tests
Using Netperf to Measure Request/Response
Options Common to TCP UDP and SCTP _RR tests
Using Netperf to Measure Aggregate Performance
Using Netperf to Measure Bidirectional Transfer
Other Netperf Tests
Netperf is a benchmark that can be use to measure various aspect of networking performance. The primary foci are bulk (aka unidirectional) data transfer and request/response performance using either TCP or UDP and the Berkeley Sockets interface. As of this writing, the tests available either unconditionally or conditionally include:
While not every revision of netperf will work on every platform listed, the intention is that at least some version of netperf will work on the following platforms:
Netperf is maintained and informally supported primarily by Rick Jones, who can perhaps be best described as Netperf Contributing Editor. Non-trivial and very appreciated assistance comes from others in the network performance community, who are too numerous to mention here. While it is often used by them, netperf is NOT supported via any of the formal Hewlett-Packard support channels. You should feel free to make enhancements and modifications to netperf to suit your nefarious porpoises, so long as you stay within the guidelines of the netperf copyright. If you feel so inclined, you can send your changes to netperf-feedback for possible inclusion into subsequent versions of netperf.
If you would prefer to make contributions to networking benchmark using certified “open source” license, please considuer netperf4, which is distributed under the terms of the GPL.
The netperf-talk mailing list is available to discuss the care and feeding of netperf with others who share your interest in network performance benchmarking. The netperf-talk mailing list is a closed list and you must first subscribe by sending email to netperf-talk-request.
A sizespec is a one or two item, comma-separated list used as an argument to a command-line option that can set one or two, related netperf parameters. If you wish to set both parameters to separate values, items should be separated by a comma:
parameter1,parameter2
If you wish to set the first parameter without altering the value of the second from its default, you should follow the first item with a comma:
parameter1,
Likewise, precede the item with a comma if you wish to set only the second parameter:
,parameter2
An item with no commas:
parameter1and2
will set both parameters to the same value. This last mode is one of the most frequently used.
There is another variant of the comma-separated, two-item list called a optionspec which is like a sizespec with the exception that a single item with no comma:
parameter1
will only set the value of the first parameter and will leave the second parameter at its default value.
Netperf has two types of command-line options. The first are global command line options. They are essentially any option not tied to a particular test or group of tests. An example of a global command-line option is the one which sets the test type - -t.
The second type of options are test-specific options. These are options which are only applicable to a particular test or set of tests. An example of a test-specific option would be the send socket buffer size for a TCP_STREAM test.
Global command-line options are specified first with test-specific
options following after a -- as in:
netperf <global> -- <test-specific>
Netperf's primary form of distribution is source code. This allows installation on systems other than those to which the authors have ready access and thus the ability to create binaries. There are two styles of netperf installation. The first runs the netperf server program - netserver - as a child of inetd. This requires the installer to have sufficient privileges to edit the files /etc/services and /etc/inetd.conf or their platform-specific equivalents.
The second style is to run netserver as a standalone daemon. This second method does not require edit privileges on /etc/services and /etc/inetd.conf but does mean you must remember to run the netserver program explicitly after every system reboot.
This manual assumes that those wishing to measure networking performance already know how to use anonymous FTP and/or a web browser. It is also expected that you have at least a passing familiarity with the networking protocols and interfaces involved. In all honesty, if you do not have such familiarity, likely as not you have some experience to gain before attempting network performance measurements. The excellent texts by authors such as Stevens, Fenner and Rudoff and/or Stallings would be good starting points. There are likely other excellent sources out there as well.
Gzipped tar files of netperf sources can be retrieved via anonymous FTP for “released” versions of the bits. Pre-release versions of the bits can be retrieved via anonymous FTP from the experimental subdirectory.
For convenience and ease of remembering, a link to the download site is provided via the NetperfPage
The bits corresponding to each discrete release of netperf are tagged for retrieval via subversion. For example, there is a tag for the first version corresponding to this version of the manual - netperf 2.4.3. Those wishing to be on the bleeding edge of netperf development can use subversion to grab the top of trunk.
There are likely other places around the Internet from which one can download netperf bits. These may be simple mirrors of the main netperf site, or they may be local variants on netperf. As with anything one downloads from the Internet, take care to make sure it is what you really wanted and isn't some malicious Trojan or whatnot. Caveat downloader.
As a general rule, binaries of netperf and netserver are not distributed from ftp.netperf.org. From time to time a kind soul or souls has packaged netperf as a Debian package available via the apt-get mechanism or as an RPM. I would be most interested in learning how to enhance the makefiles to make that easier for people, and perhaps to generate HP-UX swinstall“depots.”
Once you have downloaded the tar file of netperf sources onto your system(s), it is necessary to unpack the tar file, cd to the netperf directory, run configure and then make. Most of the time it should be sufficient to just:
gzcat <netperf-version>.tar.gz | tar xf -
cd <netperf-version>
./configure
make
make install
Most of the “usual” configure script options should be present dealing with where to install binaries and whatnot.
./configure --help
should list all of those and more.
If the netperf configure script does not know how to automagically
detect which CPU utilization mechanism to use on your platform you may
want to add a --enable-cpuutil=mumble option to the configure
command. If you have knowledge and/or experience to contribute to
that area, feel free to contact netperf-feedback@netperf.org.
Similarly, if you want tests using the XTI interface, Unix Domain
Sockets, DLPI or SCTP it will be necessary to add one or more
--enable-[xti|unix|dlpi|sctp]=yes options to the configure
command. As of this writing, the configure script will not include
those tests automagically.
On some platforms, it may be necessary to precede the configure command with a CFLAGS and/or LIBS variable as the netperf configure script is not yet smart enough to set them itself. Whenever possible, these requirements will be found in README.platform files. Expertise and assistance in making that more automagical in the configure script would be most welcome.
Other optional configure-time settings include
--enable-intervals=yes to give netperf the ability to “pace”
its _STREAM tests and --enable-histogram=yes to have netperf
keep a histogram of interesting times. Each of these will have some
effect on the measured result. If your system supports
gethrtime() the effect of the histogram measurement should be
minimized but probably still measurable. For example, the histogram
of a netperf TCP_RR test will be of the individual transaction times:
netperf -t TCP_RR -H lag -v 2
TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to lag.hpl.hp.com (15.4.89.214) port 0 AF_INET : histogram
Local /Remote
Socket Size Request Resp. Elapsed Trans.
Send Recv Size Size Time Rate
bytes Bytes bytes bytes secs. per sec
16384 87380 1 1 10.00 3538.82
32768 32768
Alignment Offset
Local Remote Local Remote
Send Recv Send Recv
8 0 0 0
Histogram of request/response times
UNIT_USEC : 0: 0: 0: 0: 0: 0: 0: 0: 0: 0
TEN_USEC : 0: 0: 0: 0: 0: 0: 0: 0: 0: 0
HUNDRED_USEC : 0: 34480: 111: 13: 12: 6: 9: 3: 4: 7
UNIT_MSEC : 0: 60: 50: 51: 44: 44: 72: 119: 100: 101
TEN_MSEC : 0: 105: 0: 0: 0: 0: 0: 0: 0: 0
HUNDRED_MSEC : 0: 0: 0: 0: 0: 0: 0: 0: 0: 0
UNIT_SEC : 0: 0: 0: 0: 0: 0: 0: 0: 0: 0
TEN_SEC : 0: 0: 0: 0: 0: 0: 0: 0: 0: 0
>100_SECS: 0
HIST_TOTAL: 35391
Long-time users of netperf will notice the expansion of the main test header. This stems from the merging-in of IPv6 with the standard IPv4 tests and the addition of code to specify addressing information for both sides of the data connection.
The histogram you see above is basically a base-10 log histogram where we can see that most of the transaction times were on the order of one hundred to one-hundred, ninety-nine microseconds, but they were occasionally as long as ten to nineteen milliseconds
The --enable-demo=yes configure option will cause code to be included to report interim results during a test run. The rate at which interim results are reported can then be controlled via the global -D option. Here is an example of –enable-demo mode output:
src/netperf -D 1.35 -H lag -f M
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to lag.hpl.hp.com (15.4.89.214) port 0 AF_INET : demo
Interim result: 9.66 MBytes/s over 1.67 seconds
Interim result: 9.64 MBytes/s over 1.35 seconds
Interim result: 9.58 MBytes/s over 1.36 seconds
Interim result: 9.51 MBytes/s over 1.36 seconds
Interim result: 9.71 MBytes/s over 1.35 seconds
Interim result: 9.66 MBytes/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim result: 9.61 MBytes/s over 1.36 seconds
Recv Send Send
Socket Socket Message/s over 1.36 seconds
Interim