Version 1 (modified by 13 years ago) (diff) | ,
---|
Continuation Round 1
In this round, I ran plastic-104 over the weekend as a simple test that anything at all was working.
The raw logs are at http://www.gpolab.bbn.com/plastic-slices/continuation/round-1/.
plastic-104
SteadyPerf UDP, using port=5104, time=518400, rate=3, and this table of client/server pairs:
client | server | server address |
ganel.gpolab.bbn.com | wings-openflow-2.wail.wisc.edu | server=10.42.104.95 |
wings-openflow-3.wail.wisc.edu | orbitplc2.orbit-lab.org | server=10.42.104.112 |
orbitplc1.orbit-lab.org | pl4.myplc.grnoc.iu.edu | server=10.42.104.72 |
pl5.myplc.grnoc.iu.edu | sardis.gpolab.bbn.com | server=10.42.104.53 |
One-time prep commands run on each client and server
sudo yum -y install iperf
Commands run on each server
server=<ipaddr> nice -n 19 iperf -u -B $server -p 5104 -s -i 1
Commands run on each client
server=<ipaddr> nice -n 19 iperf -u -c $server -p 5104 -t 518400 -b 3M
Results
Generated with
subnet=104 for host in $(awk 'NR%2==1' ~/plastic-slices/logins/logins-plastic-$subnet.txt | sed -r -e 's/.+@//') ; do echo -e "$host:\n\n{{{" ; grep -A 10 -B 1 "Client connecting" pgenigpolabbbncom_plastic$subnet\@$host.log ; echo -e "}}}\n" ; done
and then edited slightly to remove artifacts (like control characters, my prompt, etc).
(This works because the summary of the results are in the client logs, and the clients are the odd-numbered lines in list of logins.)
ganel.gpolab.bbn.com:
------------------------------------------------------------ Client connecting to 10.42.104.95, UDP port 5104 Sending 1470 byte datagrams UDP buffer size: 110 KByte (default) ------------------------------------------------------------ [ 3] local 10.42.104.51 port 51990 connected with 10.42.104.95 port 5104 [ 3] 0.0-264174.3 sec 92.3 GBytes 3.00 Mbits/sec [ 3] Sent 67391400 datagrams [ 3] Server Report: [ 3] 0.0-264173.5 sec 91.2 GBytes 2.97 Mbits/sec 0.026 ms 782044/67391400 (1.2%) [ 3] 0.0-264173.5 sec 376 datagrams received out-of-order
wings-openflow-3.wail.wisc.edu:
------------------------------------------------------------ Client connecting to 10.42.104.112, UDP port 5104 Sending 1470 byte datagrams UDP buffer size: 110 KByte (default) ------------------------------------------------------------ [ 3] local 10.42.104.96 port 37921 connected with 10.42.104.112 port 5104 [ ID] Interval Transfer Bandwidth [ 3] 0.0-264181.9 sec 92.3 GBytes 3.00 Mbits/sec [ 3] Sent 67393353 datagrams [ 3] Server Report: [ 3] 0.0-264181.0 sec 91.4 GBytes 2.97 Mbits/sec 0.022 ms 661709/67393352 (0.98%) [ 3] 0.0-264181.0 sec 385 datagrams received out-of-order
orbitplc1.orbit-lab.org:
------------------------------------------------------------ Client connecting to 10.42.104.72, UDP port 5104 Sending 1470 byte datagrams UDP buffer size: 110 KByte (default) ------------------------------------------------------------ [ 3] local 10.42.104.111 port 45609 connected with 10.42.104.72 port 5104 [ 3] 0.0-264182.6 sec 92.3 GBytes 3.00 Mbits/sec [ 3] Sent 67393513 datagrams [ 3] Server Report: [ 3] 0.0-264181.9 sec 92.3 GBytes 3.00 Mbits/sec 0.007 ms 1095/67393513 (0.0016%) [ 3] 0.0-264181.9 sec 1095 datagrams received out-of-order
pl5.myplc.grnoc.iu.edu:
------------------------------------------------------------ Client connecting to 10.42.104.53, UDP port 5104 Sending 1470 byte datagrams UDP buffer size: 110 KByte (default) ------------------------------------------------------------ [ 3] local 10.42.104.73 port 50850 connected with 10.42.104.53 port 5104 [ 3] 0.0-264183.0 sec 92.3 GBytes 3.00 Mbits/sec [ 3] Sent 67393628 datagrams [ 3] Server Report: [ 3] 0.0-264182.1 sec 92.1 GBytes 2.99 Mbits/sec 0.015 ms 119984/67393628 (0.18%) [ 3] 0.0-264182.1 sec 136 datagrams received out-of-order
Analysis
There appear to have been two gaps in the two pairs that include Wisconsin: One of about eight minutes, and one of about 43 minutes. The raw logs have more details.