From 8f70def3aa5fd27bd975a5cdbac557ee8da4441d Mon Sep 17 00:00:00 2001 From: Kshithij Iyer Date: Fri, 13 Sep 2019 12:41:29 +0530 Subject: [PATCH] Fixing 404 links in Performance Testing.md --- docs/Administrator Guide/Performance Testing.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/Administrator Guide/Performance Testing.md b/docs/Administrator Guide/Performance Testing.md index c929a61..b92dc3c 100644 --- a/docs/Administrator Guide/Performance Testing.md +++ b/docs/Administrator Guide/Performance Testing.md @@ -335,10 +335,8 @@ cluster lifecycle. Fortunately, can be enhanced significantly, often without additional hardware. To measure network performance, consider use of a -[netperf-based](http://www.netperf.org/netperf/NetperfPage.html) -script such as -* [network-stream-pairs.sh](https://github.com/bengland2/parallel-libgfapi/blob/master/netperf-stream-pairs.sh) - sets up unidirectional TCP streams between pairs of hosts -* [network-rpc-pairs.sh](https://github.com/bengland2/parallel-libgfapi/blob/master/netperf-rpc-pairs.sh) - sets up request-response flows between pairs of hosts +[netperf-based](http://www.cs.kent.edu/~farrell/dist/ref/Netperf.html) +script. The purpose of these two tools is to characterize the capacity of your entire network infrastructure to support the desired level of traffic induced by distributed storage, using multiple network connections in parallel. The latter script is probably the most realistic network workload for distributed storage.