Changes between Version 5 and Version 6 of PlasticSlices/Experiments

Timestamp:

05/18/11 13:40:38 (13 years ago)

Author:

Josh Smift

Comment:

--

PlasticSlices/Experiments

@@ -11 +11 @@
 == Setup ==
 
-Divide the hosts that you want to use into pairs. The client is the one that you'll run the 'ping' command on; the server is the one that you'll ping from the client.
+Divide the hosts that you want to use into pairs. In each pair, the client is the one that you'll run the 'ping' command on, and the server is the one that you'll ping from the client.
 
 Identify the precise IP address on each server that you'll want to ping. Make a table to keep track of which server you'll want to ping from each client, e.g.
 
 || '''client'''                   || '''server'''                   || '''server address''' ||
-|| ganel.gpolab.bbn.com           || planetlab5.clemson.edu         || server=10.42.101.105 ||
-|| planetlab4.clemson.edu         || pl5.myplc.grnoc.iu.edu         || server=10.42.101.73  ||
-|| of-planet1.stanford.edu        || wings-openflow-3.wail.wisc.edu || server=10.42.101.96  ||
+|| ganel.gpolab.bbn.com           || planetlab5.clemson.edu         || server=10.42.17.105  ||
+|| planetlab4.clemson.edu         || pl5.myplc.grnoc.iu.edu         || server=10.42.17.73   ||
+|| of-planet1.stanford.edu        || wings-openflow-3.wail.wisc.edu || server=10.42.17.96   ||
 
 You'll use the "server=<ipaddr>" parts when you run the experiment.
@@ -67 +67 @@
 == Setup ==
 
-Divide the hosts that you want to use into pairs. You'll run a netcat listener on the server, and make a netcat connection to it from the client.
+Divide the hosts that you want to use into pairs. In each pair, you'll run a netcat listener on the server, and make a netcat connection to it from the client.
 
 Identify the precise IP address on each server that you'll want to connect to. Make a table to keep track of which server you'll want to connect to from each client, e.g.
 
 || '''client'''                   || '''server'''                   || '''server address''' ||
-|| ganel.gpolab.bbn.com           || planetlab5.clemson.edu         || server=10.42.101.105 ||
-|| planetlab4.clemson.edu         || pl5.myplc.grnoc.iu.edu         || server=10.42.101.73  ||
-|| of-planet1.stanford.edu        || wings-openflow-3.wail.wisc.edu || server=10.42.101.96  ||
+|| ganel.gpolab.bbn.com           || planetlab5.clemson.edu         || server=10.42.17.105  ||
+|| planetlab4.clemson.edu         || pl5.myplc.grnoc.iu.edu         || server=10.42.17.73   ||
+|| of-planet1.stanford.edu        || wings-openflow-3.wail.wisc.edu || server=10.42.17.96   ||
 
 You'll use the "server=<ipaddr>" parts when you run the experiment.
@@ -164 +164 @@
 == Setup ==
 
-Divide the hosts that you want to use into pairs. You'll run an HTTPS server on the server, and run wget on the client to fetch files from it.
+Divide the hosts that you want to use into pairs. In each pair, you'll run an HTTPS server on the server, and run wget on the client to fetch files from it.
 
 Identify the precise IP address on each server that you'll want to connect to. Make a table to keep track of which server you'll want to connect to from each client, e.g.
 
 || '''client'''                   || '''server'''                   || '''server address''' ||
-|| ganel.gpolab.bbn.com           || planetlab5.clemson.edu         || server=10.42.101.105 ||
-|| planetlab4.clemson.edu         || pl5.myplc.grnoc.iu.edu         || server=10.42.101.73  ||
-|| of-planet1.stanford.edu        || wings-openflow-3.wail.wisc.edu || server=10.42.101.96  ||
+|| ganel.gpolab.bbn.com           || planetlab5.clemson.edu         || server=10.42.17.105  ||
+|| planetlab4.clemson.edu         || pl5.myplc.grnoc.iu.edu         || server=10.42.17.73   ||
+|| of-planet1.stanford.edu        || wings-openflow-3.wail.wisc.edu || server=10.42.17.96   ||
 
 You'll use the "server=<ipaddr>" parts when you run the experiment.
@@ -293 +293 @@
 This experiment uses the iperf command to send 1 GB of data via TCP, measuring performance throughout the transfer.
 
+== Setup ==
+
+Divide the hosts that you want to use into pairs. In each pair, you'll run an iperf listener on the server, and make an iperf connection to it from the client.
+
+Identify the precise IP address on each server that you'll want to connect to. Make a table to keep track of which server you'll want to connect to from each client, e.g.
+
+|| '''client'''                   || '''server'''                   || '''server address''' ||
+|| ganel.gpolab.bbn.com           || planetlab5.clemson.edu         || server=10.42.17.105  ||
+|| planetlab4.clemson.edu         || pl5.myplc.grnoc.iu.edu         || server=10.42.17.73   ||
+|| of-planet1.stanford.edu        || wings-openflow-3.wail.wisc.edu || server=10.42.17.96   ||
+
+You'll use the "server=<ipaddr>" parts when you run the experiment.
+
+Identify a port that you'd like to use for the connection; call it <port>, and use it below when you run the iperf server and client commands.
+
+Divide 1000 by the number of host pairs you have (the number of rows in your table); call this number <size>, and use it below when you run the iperf client command. (This is how much data (in megabytes) each client will send to the server.)
+
+On each client and server, install iperf:
+
+{{{
+sudo yum -y install iperf
+}}}
+
+== Execution ==
+
+On each server, run
+
+{{{
+server=<ipaddr>
+nice -n 19 iperf -B $server -p <port> -s -i 1
+}}}
+
+using the "server=<ipaddr>" line from your table, and the <port> value you identified earlier. That should print a few lines on your terminal immediately, including ones like
+
+{{{
+Server listening on TCP port <port>
+Binding to local address <ipaddr>
+}}}
+
+and then more lines once a client connects.
+
+On each client, run
+
+{{{
+nice -n 19 iperf -c $server -p <port> -n <size>M
+}}}
+
+using the "server=<ipaddr>" line from your table, and the <port> value you identified earlier. That should print a few lines on your terminal immediately, including ones like
+
+{{{
+Client connecting to <ipaddr>, TCP port <port>
+------------------------------------------------------------
+[  3] local 10.42.17.51 port 40997 connected with <ipaddr> port <port>
+}}}
+
+The client IP address and port will be different, of course.
+
+The server will then start to print lines like
+
+{{{
+[  4] local <ipaddr> port <port> connected with 10.42.17.51 port 40997
+[  4]  0.0- 1.0 sec    359 KBytes  2.94 Mbits/sec
+[  4]  1.0- 2.0 sec    498 KBytes  4.08 Mbits/sec
+}}}
+
+When the transfer finishes, the client will print lines like
+
+{{{
+[ ID] Interval       Transfer     Bandwidth
+[  3]  0.0- 2.2 sec  1.00 MBytes  3.79 Mbits/sec
+}}}
+
+Copy that final block for your results.
+
+When the transfer finishes, on the server, hit ctrl-c to kill the iperf server process.
+
+''FIXME: It would be better if this piped to 'tee', so that you get log files for free.''
+
+== Results ==
+
+The results of the experiment are the three-line statistics summary at the end of the output on the client.
+
+''FIXME: Do we also want to capture the output from the server.''
+
+== Cleanup ==
+
+No special cleanup is needed.
+
 = GigaPerfUDP =
 
 This experiment uses the iperf command to send 1 GB of data via UDP, measuring performance throughout the transfer.
+
+== Setup ==
+
+Divide the hosts that you want to use into pairs. In each pair, you'll run an iperf listener on the server, and make an iperf connection to it from the client.
+
+Identify the precise IP address on each server that you'll want to connect to. Make a table to keep track of which server you'll want to connect to from each client, e.g.
+
+|| '''client'''                   || '''server'''                   || '''server address''' ||
+|| ganel.gpolab.bbn.com           || planetlab5.clemson.edu         || server=10.42.17.105  ||
+|| planetlab4.clemson.edu         || pl5.myplc.grnoc.iu.edu         || server=10.42.17.73   ||
+|| of-planet1.stanford.edu        || wings-openflow-3.wail.wisc.edu || server=10.42.17.96   ||
+
+You'll use the "server=<ipaddr>" parts when you run the experiment.
+
+Identify a port that you'd like to use for the connection; call it <port>, and use it below when you run the iperf server and client commands.
+
+Divide 1000 by the number of host pairs you have (the number of rows in your table); call this number <size>, and use it below when you run the iperf client command. (This is how much data (in megabytes) each client will send to the server.)
+
+Decide how fast you'd like to send data (in megabits per second); call this number <rate>, and use it below when you run the iperf client command.
+
+On each client and server, install iperf:
+
+{{{
+sudo yum -y install iperf
+}}}
+
+== Execution ==
+
+On each server, run
+
+{{{
+server=<ipaddr>
+nice -n 19 iperf -u -B $server -p <port> -s -i 1
+}}}
+
+using the "server=<ipaddr>" line from your table, and the <port> value you identified earlier. That should print a few lines on your terminal immediately, including ones like
+
+{{{
+Server listening on UDP port <port>
+Binding to local address <ipaddr>
+}}}
+
+and then more lines once a client connects.
+
+On each client, run
+
+{{{
+nice -n 19 iperf -u -c $server -p <port> -n <size>M -b <rate>M
+}}}
+
+using the "server=<ipaddr>" line from your table, and the <port>, <size>, and <rate> values you identified earlier. That should print a few lines on your terminal immediately, including ones like
+
+{{{
+Client connecting to <ipaddr>, UDP port <port>
+------------------------------------------------------------
+[  3] local 10.42.17.51 port 40997 connected with <ipaddr> port <port>
+}}}
+
+The client IP address and port will be different, of course.
+
+The server will then start to print lines like
+
+{{{
+[  4] local <ipaddr> port <port> connected with 10.42.17.51 port 40997
+[  4]  0.0- 1.0 sec    359 KBytes  2.94 Mbits/sec
+[  4]  1.0- 2.0 sec    498 KBytes  4.08 Mbits/sec
+}}}
+
+When the transfer finishes, the client will print lines like
+
+{{{
+[ ID] Interval       Transfer     Bandwidth
+[  3]  0.0-79.8 sec   954 MBytes   100 Mbits/sec
+[  3] Sent 680273 datagrams
+[  3] Server Report:
+[  3]  0.0-79.1 sec   881 MBytes  93.4 Mbits/sec   0.040 ms 52088/680272 (7.7%)
+[  3]  0.0-79.1 sec  256 datagrams received out-of-order
+}}}
+
+Copy that final block for your results.
+
+When the transfer finishes, on the server, hit ctrl-c to kill the iperf server process.
+
+''FIXME: It would be better if this piped to 'tee', so that you get log files for free.''
+
+== Results ==
+
+The results of the experiment are the three-line statistics summary at the end of the output on the client.
+
+''FIXME: Do we also want to capture the output from the server.''
+
+== Cleanup ==
+
+No special cleanup is needed.