summaryrefslogtreecommitdiffstats
path: root/cluster/netpipe/DETAILS
diff options
context:
space:
mode:
Diffstat (limited to 'cluster/netpipe/DETAILS')
-rwxr-xr-xcluster/netpipe/DETAILS30
1 files changed, 30 insertions, 0 deletions
diff --git a/cluster/netpipe/DETAILS b/cluster/netpipe/DETAILS
new file mode 100755
index 0000000000..90c5b4c1dd
--- /dev/null
+++ b/cluster/netpipe/DETAILS
@@ -0,0 +1,30 @@
+ SPELL=netpipe
+ VERSION=3.6
+ SOURCE=NetPIPE\_$VERSION.tar.gz
+ MD5[0]=340217f71c613b4c2d796eadcd360f6c
+SOURCE_DIRECTORY=$BUILD_DIRECTORY/${SOURCE/\.tar.gz/}
+ SOURCE_URL[0]=http://www.scl.ameslab.gov/Projects/NetPIPE/code/$SOURCE
+ WEB_SITE=http://www.scl.ameslab.gov/Projects/NetPIPE/
+ ENTERED=20020606
+ UPDATED=20020606
+ MAINTAINER=zoran@idi.ntnu.no
+ LICENSE=GPL
+ SHORT="network performance tool"
+cat << EOF
+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.
+
+Interfaces are available for TCP, PVM and MPI.
+
+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 comm. protocol layer(s)?
+how quickly will a small (< 1 kbyte) control message arrive,
+and which network and protocol are best for this purpose?
+EOF