Changes between Version 21 and Version 22 of GENIOESSTopologiesPerformance


Ignore:
Timestamp:
06/17/14 16:57:41 (5 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIOESSTopologiesPerformance

    v21 v22  
    22
    33This page capture a summary of the performance measurements collected while running the test cases listed in the [wiki:GENIOESSTopologiesTestStatus] page.
    4 
    5 Traffic Characteristics for October 2013 tests:
     4Traffic Characteristics:
    65{{{
    76   iperf -c destaddr -t 60
     
    98   ping  destaddr -q -c 60
    109}}}
    11 The iperf tests performed on 2014-02-14 expand the iperf tests to add 2 additional tests for 5 and 10 TCP clients.
    1210
    13 
    14 == AL2S to AL2S Performance to Test End-Point ==
     11== AL2S Test End-Point to AL2S Performance Test End-Point ==
    1512Collected: 2013-10-24   
    1613Performance data collected for 4 AL2S to AL2S slivers by Luke Fowler:
     
    2219||sdn-sw.newy32aoa e15/5 <- sdn-sw.wash e15/2 ||8.21 Gbits/sec  ||101 Mbits/sec  || 5.314/5.436/10.962/0.720 ms   ||
    2320
    24 == GPO ION Site to AL2S Test End-Point Performance ==
    25 
     21== GPO IG ION Site to AL2S Test End-Point Performance ==
    2622Collected: 2013-10-24   
    2723Endpoints: GPO InstaGENI VM host (iperf client) and AL2S Atlanta test end-point (iperf server) for all three x-connects below:
     
    4137|| sdn-sw.kans e15/1 <-> rtr.kans:port=xe-0/0/3 ||70.0 Mbits/sec ||98.6 Mbits/sec      ||99.7 Mbits/sec       ||97.9 Mbits/sec||71.377/71.442/71.502/0.356 ms   ||
    4238
    43 == Stanford IG AL2S to GPO IG ION Performance ==
     39== Stanford InstaGENI AL2S to Missouri InstaGENI AL2S Performance ==
     40Collected: 2014-06-17 
     41Endpoints: Missouri InstaGENI Xen VM (iperf client) and Stanford InstaGENI Xen VM (iperf server):
     42
     43|| '''End-points'''                    ||'''1 Client(TCP)'''||'''5 Clients(TCP)'''||'''10 Clients(TCP)'''|| '''UDP'''     || '''rtt min/avg/max/mdev '''    ||
     44|| Missouri IG AL2S to Stanford IG AL2S||  39.2 Mbits/sec   || 99.6 Mbits/sec     || 99.6 Mbits/sec      || 94.4 Mbits/sec|| 39.876/40.278/42.692/0.434 ms  ||
     45|| Stanford IG AL2S to Missouri IG AL2S||  39.3 Mbits/sec   || 99.5 Mbits/sec     || 99.7 Mbits/sec      || 94.6 Mbits/sec|| 39.964/40.198/40.560/0.239 ms  ||
     46
     47== Stanford InstaGENI AL2S to GPO InstaGENI ION Performance ==
    4448Collected: 2014-06-17   
    4549Endpoints: GPO InstaGENI Xen VM (iperf client) and Stanford InstaGENI Xen VM (iperf server) via ATLA cross-connect:
     
    4953||GPO IG ION to Stanford IG AL2S || 18.2 Mbits/sec    || 91.2 Mbits/sec     || 99.2 Mbits/sec      || 93.9 Mbits/sec || 86.666/86.989/87.269/0.424 ms ||
    5054
    51 Note: recollect with raw-pc
    52 
    53 == Stanford IG AL2S to Missouri AL2S Performance ==
    54 Collected: 2014-06-17 
    55 Endpoints: Missouri InstaGENI Xen VM (iperf client) and Stanford InstaGENI Xen VM (iperf server):
    56 
    57 || '''End-points'''                    ||'''1 Client(TCP)'''||'''5 Clients(TCP)'''||'''10 Clients(TCP)'''|| '''UDP'''     || '''rtt min/avg/max/mdev '''    ||
    58 || Missouri IG AL2S to Stanford IG AL2S||  39.2 Mbits/sec   || 99.6 Mbits/sec     || 99.6 Mbits/sec      || 94.4 Mbits/sec|| 39.876/40.278/42.692/0.434 ms  ||
    59 || Stanford IG AL2S to Missouri IG AL2S||  39.3 Mbits/sec   || 99.5 Mbits/sec     || 99.7 Mbits/sec      || 94.6 Mbits/sec|| 39.964/40.198/40.560/0.239 ms  ||
    6055
    6156