Known Names for the Netperf Database
The names presented on this page are provided for solely for the
purpose of making submittals and retrievals of the netperf database
easier and less error-prone. In providing this information,
Hewlett-Packard makes NO endorsement of any kind. Please be certain
you have read the
disclaimer
before going any further.
This page contains guidelines and lists of identifiers for the various
fields in the submittal and retrieval forms. You can use this first
list to go straight to the identifier list that interests you.
Model names are free-form keywords. They should closely follow the
common name for that model and be sufficiently detailed to
differentiate one model from another. For example, at the time of
this writing, there were six different models of HP 9000/715 so
stating simply "715" would be too vague. Each differed in clock-rate,
so the model names for them would be 715/33, 715/50, and so on. The
model name does not need to include an indication of vendor.
To insure that your submittal is more easily retrieved by others, it
is suggested that you use the following identifiers to represent the
various system vendors. If you wish to submit numbers for a system
from a vendor not on this list, please feel free to do so, using a
value of "Other" and place the vendor name in the "Comments" section
of the submittal form. At the same time, please use the
feedback
page so the maintainers of the database can update this list.
When retrieving numbers, you may also use "Other" or you may try what
you think the vendor's name might be.
- Compaq
- Compaq Computer Corporation
- Dell
- Dell Computer Corporation
- DEC
- Digital Equipment Corporation
- HP
- Hewlett-Packard Corporation
- IBM
- International Business Machines
- RNS
- Rockwell Network Systems
- SGI
- Silicon Graphics Incorporated
- Sun
- Sun Microsystems Incorporated
A release numbers are free-form keywords. They should be sufficiently
detailed to allow others to order the software if they wish to
reproduce your results. For Unix operating systems, the output of
"uname -r" is often a good choice (though perhaps not for Solaris).
Your mileage will vary for other software - such as transport or
driver software.
To insure that your submittal is more easily retrieved by others, it
is suggested that you use the following identifiers to represent the
various operating systems. If you wish to submit numbers for a system
running an OS not on this list, please feel free to do so, using an
identifier of "Other" and include the real name in the Comments
section. At the same time,please use the
feedback
page so the maintainers of the database can update this list.
When retrieving numbers, you may also use "Other" or you may try what
you think the OS name might be.
- AIX
- BSD
- FreeBSD
- HP-RT
- HP-UX
- IRIX
- Linux
- MPE/iX
- MS-DOS
- NetBSD
- NT
- OSF
- SCO
- Solaris
- SunOS
- Unixware
- Windows
The following are the currently known Transport Vendors. Please use
these names when accessing the database. If the transport software
came with the operating system, use the term "Bundled." If the
transport software came from a vendor not on this list, use the term
"Other" and list the name of the transport provider in the Comments
section. Please use the
feedback
page to let the maintainers know to update this list.
- Bundled
- The transport software came bundled with the system. This is
often the case with Unix systems, but not so with PC's.
- B&W
- Beame & Whiteside
- FTP
- FTP Software Inc.
- NetManage
- NetManage
- SunConnect
- SunConnect
To insure that your submittal is more easily retrieved by others, it
is suggested that you use the following identifiers to represent the
various network interface vendors. If you wish to submit numbers for a
card from a vendor not on this list, please feel free to do so,
using an identifier of "Other" and include the real name in the
Comments section. At the same time, please use the
feedback
page so the maintainers of the database can update this list.
When retrieving numbers, you may also use "Other" or you may try what
you think the card vendor's name might be.
- Ancor
- Ancor Communications Inc.
- Cicso
- Cisco Systems Inc.
- DEC
- Digital Equipemnt Corporation
- Efficient
- Efficient Networks Inc.
- Fore
- Fore Systems Inc.
- Genroco
- GENROCO In.
- HP
- Hewlett-Packard Company
- IBM
- International Business Machines
- Interphase
- Interphase Corpration
- Myricom
- NPI
- Network Peripherals Inc.
- RNS
- Rockwell Network Systems
- SGI
- Silicon Graphics Inc.
- Sun
- Sun Microsystems Inc.
- Synoptics
To insure that your submittal is more easily retrieved by others, it
is suggested that you use the following identifiers to represent the
various I/O busses. If you wish to submit numbers for an I/O bus not
on this list, please feel free to do so, using an identifier of
"Other" and include the real name in the Comments section. At the same
time, please use the
feedback
page so the maintainers of the database can update this list.
When retrieving numbers, you may also use "Other" or you may try what
you think the bus name might be.
- Core
- EISA
- GIO
- GSC/GSC+
- HIO
- ISA
- MCA
- NIO
- PCI
- SBUS
- TURBOchannel
- VESA
- VME
- XIO
To insure that your submittal is more easily retrieved by others, it
is suggested that you use the following identifiers to represent the
various network types. If you wish to submit numbers for a network
type not on this list, please feel free to do so, using an identifier
of "Other" and include the real name in the Comments section. At the
same time, please use the
feedback
page so the maintainers of the database can update this list.
When retrieving numbers, you may also use "Other" or you may try what
you think the network name might be.
Please use the comments section to describe any
switches, routers, or
other interesting interconnect devices between the system running
netperf and the system running netserver. If the systems were
connected back-to-back then please indicate so in the
comments.
- ATM
- Asynchronous Transfer Mode running at an unknown rate or
different rates at either end.
- ATM-25
- Asynchronous Transfer Mode running at ~25 Mbit/s. (Was ATM)
- ATM-51
- Asynchronous Transfer Mode running at ~51 Mbit/s. (Was ATM)
- ATM-100
- Asynchronous Transfer Mode running at ~100 Mbit/s (TAXI). (Was ATM)
- ATM-155
- Asynchronous Transfer Mode running at ~155 Mbit/s (SONET). (Was ATM)
- ATM-622
- Asynchronous Transfer Mode running at ~622 Mbit/s. (Was ATM)
- Ethernet
- "Classic" 10 Mbit/s Ethernet. Includes 10BaseT, 10Base2 and
10BaseF. If full-duplex please indicate so in
the Comments section of the submittal form.
- 100VG
- 100 Mbit/s 100VG-AnyLAN (a.k.a. IEEE 802.12) Please specify
either Ethernet or TokenRing (802.5) framing in the Comments
section. If full-duplex indicate so in
the Comments section of the submittal form.
- GigabitEthernet
- 1000 Mbit/s Ethernet.
- FastEthernet
- 100 Mbit/s Ethernet using CSMA/CD (100BaseT, 100BaseX, etc). If
full-duplex please indicate so in the Comments
section of the submittal form.
- FDDI
- FDDI (or CDDI) running over Fiber, UTP Copper or STP (Was
FDDI/CDDI). Please state if the connection was dual-attach, or
single-attach, and the type of concentrator used (if any).
- FC
- Fibre Channel running at an unknown rate, or at different rates
at either end.
- FC-266
- Fibre Channel running at ~266 Mbit/s (25 MB/s). Also known as
"quarter-speed." (Was FibreChannel)
- FC-531
- Fibre Channel running at ~531 Mbit/s (50 MB/s). Also known as
"half-speed." (Was FibreChannel)
- FC-1062
- Fibre Channel running at ~1062 Mbit/s (100 MB/s). Also known as
"full-speed." (Was FibreChannel)
- HiPPI
- Hi Performance Parallel Interface
- Loopback
- Myrinet
- SLIP/PPP
- Serial Line IP or Point-to-Point Protocol. Specify the
uncompressed and compressed speed of the modems being used in
the Comments section. This includes CSLIP
- 802.5-4
- 802.5 Token Ring (IBM Token Ring) running at ~4 Mbit/s
- 802.5-16
- 802.5 Token Ring (IBM Token Ring) running at `16 Mbit/s
To insure that your submittal is more easily retrieved by others, it
is suggested that you use the following identifiers to represent the
various test types. If you wish to submit numbers for a test
type not on this list, please feel free to do so, using an identifier
of "Other" and an explanation in the Comments section. At the same
time, please use the
feedback
page so the maintainers of the database can update this list.
- TCP_STREAM
- A TCP_STREAM test is a unidirecitonal data transfer test using
the Transmission Control Protocol and the Berkeley Sockets API.
- TCP_RR
- A TCP_RR test is a synchronous request/response test which can
be used to measure end-to-end round trip latency using the BSD API.
- UDP_STREAM
- A UDP_STREAM test is a unidirecitonal data transfer test using
the User Datagram Protocol and the BSD API.
- UDP_RR
- A UDP_RR test is a synchronous request/response test which can
be used to measure end-to-end round trip latency using the BSD
API.
- DLCO_STREAM
- A DLCO_STREAM test is a unidirecitonal data transfer test using
the DLPI Connection Oriented API (802.2 Type 2). It is
analagous to a TCP_STREAM test.
- DLCO_RR
- DLCL_STREAM
- A DLCL_STREAM test is a unidirecitonal data transfer test using
the DLPI ConnectionLess API (802.2 Type 1). It is analgous to a
UDP_STREAM test.
- DLCL_RR
- STREAM_STREAM
- A STREAM_STREAM test is a unidirecitonal data transfer test using
the Unix Domain Sockets API and stream semantics.
- STREAM_RR
- DG_STREAM
- A DG_STREAM test is a unidirecitonal data transfer test using
the Unic Domain Sockets API and datagram semantics.
- DG_RR
- FORE_STREAM
- A FORE_STREAM test is a unidirecitonal data transfer test using
the Fore ATM API. It is analagous to a UDP_STREAM test.
- FORE_RR
- HIPPI_STREAM
- A HIPPI_STREAM test is a unidirecitonal data transfer test using
the HP HiPPI LLA API
- HIPPI_RR
- Other
If you have ideas on how to improve this page, please feel free to
provide your
feedback.
Netperf Homepage.