> I also used netperf but it measures the throughput.
The _default_ test type in netperf is a TCP_STREAM test that indeed is
a througput test. However, there is also the TCP_RR test which is a
test very much like ping, only from application to application.
$ netperf -t TCP_RR -H <host>
is the simplest version of that. It will report average transactions
per second over the test interval. You can also use the -r option to
set the request and/or response size:
$ netperf -t TCP_RR -H <host> -- -r 128,256
will send 128 byte requests and receive 256 byte responses. A number
with no comma sets both to the same value. The default is one byte
each way.
If you compile netperf with -DHISTOGRAM it will keep a "logarithmic"
histogram of individual round-trip times and display that histogram if
you set the verbosity level to two. Here is an example of a test
between a machine in Palo Alto and one in Cupertino just to make it
more interesting:
TCP REQUEST/RESPONSE TEST to tardy.cup.hp.com : 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 926.78
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: 0: 0: 0: 0: 0: 0: 0: 1540: 2823
UNIT_MSEC : 0: 4759: 123: 24: 2: 1: 0: 0: 0: 0
TEN_MSEC : 0: 0: 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
Quote:>100_SECS: 0
HIST_TOTAL: 9272
Of course, it won't necessarily tell you what is going on, just that something
was going-on with that test at that time.
happy benchmarking,
rick jones
--
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to raj in cup.hp.com but NOT BOTH...