Xref: utzoo comp.protocols.tcp-ip:15558 comp.unix.wizards:24733
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!vjs@rhyolite.wpd.sgi.com
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Newsgroups: comp.protocols.tcp-ip,comp.unix.wizards
Subject: Re: TCP benchmarking
Summary: yet another benchmark idea
Message-ID: <96122@sgi.sgi.com>
Date: 8 Apr 91 23:40:19 GMT
References: <4188@stl.stc.co.uk>
Sender: guest@sgi.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 22


I've encountered another "benchmark."

First try the 4.3BSD `ping -l9999999 target` and look at the packet rate.
There are commercially available UNIX workstations that will deliver the
vast majority of the zillion 98-byte ether packets separated by only 9.6
microseconds.  The point is I think there are several vendors'
workstatsions that can write at or close to ethernet media speed, <<from a
user process>>.

Second, modify the more recent 4.3BSD-tahoe or reno ping.c to flush the "."
and "\b" characters only occassionally or when things get slow, so that
`ping -f` does not spend most of its time fiddling with stdio.  Then make
`ping -f` compute a packet/sec rate to be displayed at the end.  This
produces nice numbers that seem to vary depending on the speed of the
machines on both ends.

Neither of these are very interesting benchmarks; they're just fun.  Ttcp
is better for TCP or UDP, and FTP for overall file system and network speed.


Vernon Schryver,  vjs@sgi.com