Import of NETPIPE, a self scaling network benchmark from AMES lab.
This commit is contained in:
26
benchmarks/netpipe/Makefile
Normal file
26
benchmarks/netpipe/Makefile
Normal file
@@ -0,0 +1,26 @@
|
||||
# New ports collection makefile for: netpipe
|
||||
# Version required: 2.3
|
||||
# Date created: 20 Feb 1998
|
||||
# Whom: jkoshy
|
||||
#
|
||||
# $Id$
|
||||
|
||||
DISTNAME= netpipe-2.3
|
||||
CATEGORIES= benchmarks net
|
||||
MASTER_SITES= ftp://ftp.ameslab.gov/pub/netpipe/ \
|
||||
http://www.freebsd.org/~jkoshy/PORTS/
|
||||
|
||||
MAINTAINER= jkoshy@freebsd.org
|
||||
|
||||
# The default port builds and installs only the TCP version of
|
||||
# netpipe(1). The sources also support PVM and MPI.
|
||||
|
||||
ALL_TARGET= NPtcp
|
||||
MAN1= netpipe.1
|
||||
MANCOMPRESSED= no
|
||||
|
||||
do-install:
|
||||
${INSTALL_PROGRAM} ${WRKSRC}/NPtcp ${PREFIX}/bin/NPtcp
|
||||
${INSTALL_DATA} ${WRKSRC}/netpipe.1 ${PREFIX}/man/man1/netpipe.1
|
||||
|
||||
.include <bsd.port.mk>
|
||||
1
benchmarks/netpipe/distinfo
Normal file
1
benchmarks/netpipe/distinfo
Normal file
@@ -0,0 +1 @@
|
||||
MD5 (netpipe-2.3.tar.gz) = cf166ac7ccab491cd68ef75e0e6f466d
|
||||
1
benchmarks/netpipe/pkg-comment
Normal file
1
benchmarks/netpipe/pkg-comment
Normal file
@@ -0,0 +1 @@
|
||||
a self-scaling network benchmark
|
||||
17
benchmarks/netpipe/pkg-descr
Normal file
17
benchmarks/netpipe/pkg-descr
Normal file
@@ -0,0 +1,17 @@
|
||||
NetPIPE is a protocol independent performance tool that encapsulates
|
||||
the best of ttcp and netperf and visually represents the network
|
||||
performance under a variety of conditions. By taking the end-to-end
|
||||
application view of a network, NetPIPE clearly shows the overhead
|
||||
associated with different protocol layers. Netpipe answers such
|
||||
questions as: how soon will a given data block of size k arrive at its
|
||||
destination? Which network and protocol will transmit size k blocks
|
||||
the fastest? What is a given network's effective maximum throughput
|
||||
and saturation level? Does there exist a block size k for which the
|
||||
throughput is maximized? How much communication overhead is due to the
|
||||
network communication protocol layer(s)? How quickly will a small (< 1
|
||||
kbyte) control message arrive, and which network and protocol are best
|
||||
for this purpose?
|
||||
|
||||
For a paper fully describing NetPIPE and sample investigation of
|
||||
network performance issues using NetPIPE, see
|
||||
http://www.scl.ameslab.gov/netpipe/paper/full.html.
|
||||
1
benchmarks/netpipe/pkg-plist
Normal file
1
benchmarks/netpipe/pkg-plist
Normal file
@@ -0,0 +1 @@
|
||||
bin/NPtcp
|
||||
Reference in New Issue
Block a user