Changes between Version 2 and Version 3 of PlasticSlices/Experiments

Timestamp:

05/17/11 14:12:50 (13 years ago)

Author:

Josh Smift

Comment:

--

PlasticSlices/Experiments

@@ -13 +13 @@
 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 address''' ||
-|| ganel.gpolab.bbn.com    || server=10.42.101.104 ||
-|| of-planet1.stanford.edu || server=10.42.101.73  ||
+|| '''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  ||
 
-You'll use the "server=<ipaddr>" parts when you go to execute the experiment.
+You'll use the "server=<ipaddr>" parts when you run the experiment.
 
-To send 1 GB of data, you'll need to send a total of 666,667 1.5 KB packets. Rounding up for simplicity, divide 700,000 by the number of host pairs you have; call this number <count>, and use it below when you run the 'ping' commands.
+To send 1 GB of data, you'll need to send a total of 666,667 1.5 KB packets. Rounding up for simplicity, divide 700,000 by the number of host pairs you have (the number of rows in your table); call this number <count>, and use it below when you run the 'ping' commands.
 
 == Execution ==
@@ -27 +28 @@
 {{{
 server=<ipaddr>
-count=<count>
-sudo ping -i .001 -s $((1500-8-20)) -c $count $server
+sudo ping -i .001 -s $((1500-8-20)) -c <count> $server
 }}}
 
@@ -51 +51 @@
 Copy that final block for your results.
 
+== Results ==
+
+The results of the experiment are the three-line statistics summary at the end of the output on the client.
+
 == Cleanup ==
 
@@ -58 +62 @@
 
 This experiment uses the 'netcat' command to send 1 GB of data via unencrypted TCP.
+
+== 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.
+
+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  ||
+
+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 netcat server and client commands.
+
+Identify a file that you'd like to transfer from the servers to the clients; call it <file>. Find out how many times you'll need to copy it to get more than 1 GB:
+
+{{{
+echo $((10**9/$(du -b <file> | awk '{print $1;}')+1))
+}}}
+
+Divide that number by the number of host pairs you have (the number of rows in your table); call this number <count>, and use it below when you run the netcat client command.
+
+Copy the file to each of the servers. (When you run the experiment, you'll download it repeatedly from each of the clients.)
+
+On each client and server, install netcat:
+
+{{{
+sudo yum install nc
+}}}
+
+== Execution ==
+
+On each server, run
+
+{{{
+server=<ipaddr>
+for i in {1..<count>} ; do nc -l $server <port> < <file> ; echo "completed transfer #$i" ; md5sum <file> ; done
+}}}
+
+using the "server=<ipaddr>" line from your table, and the <count>, <port>, and <file> values you identified earlier.
+
+You won't seen any output immediately, but when you start running clients, as each transfer completes, you should see lines on your terminal that look like
+
+{{{
+completed transfer #1
+}}}
+
+and the md5sum checksum of the file.
+
+On each client, run
+
+{{{
+server=<ipaddr>
+rm -rf ~/giganetcat
+mkdir ~/giganetcat
+cd ~/giganetcat
+for i in {1..<count>} ; do nc $server <port> > <file> ; echo "completed transfer #$i" ; md5sum <file> ; mv <file> <file>.$i ; done
+}}}
+
+You won't seen any output immediately, but as each transfer completes, you should see lines on your terminal that look like
+
+{{{
+completed transfer #1
+}}}
+
+and the md5sum checksum of the file (and the filename).
+
+''FIXME: It would be better if this piped to 'tee', to make it easier to compare the output between client and server later.''
+
+== Results ==
+
+In each client-server pair, compare the output on the client and the server. They should be identical: Each should list the same set of transfers completed, and all of the md5sum lines should be identical on both.
+
+On each client, check the total size of the data transfered:
+
+{{{
+du -sb .
+}}}
+
+Add up the results for all the clients; they should add up to 1 GB (or more).
+
+''FIXME: If we had the output from both client and server in a file, we could diff them, and grep for anomalous md5sum lines.''
+
+== Cleanup ==
+
+On each client, remove the giganetcat directory:
+
+{{{
+cd
+rm -rf ~/giganetcat
+}}}
 
 = !GigaWeb =