Version 22 (modified by 9 years ago) (diff) | ,
---|
GENI AL2S/OESS Topologies Performance
This page capture a summary of the performance measurements collected while running the test cases listed in the GENIOESSTopologiesTestStatus page. Traffic Characteristics:
iperf -c destaddr -t 60 iperf -c destaddr -t 60 -b 100M -u ping destaddr -q -c 60
AL2S Test End-Point to AL2S Performance Test End-Point
Collected: 2013-10-24 Performance data collected for 4 AL2S to AL2S slivers by Luke Fowler:
Endpoint hosts | TCP | UDP | rtt min/avg/max/mdev |
sdn-sw.atla e15/3 <- sdn-sw.losa e15/3 | 9.71 Gbits/sec | 101 Mbits/sec | 54.950/55.012/55.273/0.190 ms |
sdn-sw.atla e15/3 <- sdn-sw.newy32aoa e15/5 | 9.52 Gbits/sec | 101 Mbits/sec | 18.364/18.395/18.408/0.113 ms |
sdn-sw.newy32aoa e15/5 <- sdn-sw.losa e15/3 | 9.51 Gbits/sec | 101 Mbits/sec | 116.839/204.929/287.846/40.016 ms |
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 |
GPO IG ION Site to AL2S Test End-Point Performance
Collected: 2013-10-24 Endpoints: GPO InstaGENI VM host (iperf client) and AL2S Atlanta test end-point (iperf server) for all three x-connects below:
Cross connect | TCP | UDP | rtt min/avg/max/mdev |
sdn-sw.atla e15/1 <-> rtr.atla:port=xe-0/3/0 | 71.3 Mbits/sec | 96.9 Mbits/sec | 23.238/39.284/123.874/28.394 ms |
sdn-sw.losa e1/1 <-> rtr.losa:port=et-10/0/0 | 14.2 Mbits/sec | 96.5 Mbits/sec | 135.987/140.973/148.510/2.867 ms |
sdn-sw.kans e15/1 <-> rtr.kans:port=xe-0/0/3 | 26.4 Mbits/sec | 96.9 Mbits/sec | 71.577/71.852/80.449/1.139 ms |
Collected: 2014-02-14 Endpoint: GPO InstaGENI dedicated (raw-pc) host (iperf client) and AL2S Atlanta test end-point (iperf server) for all three x-connects below:
Cross connect | 1 Client(TCP) | 5 Clients(TCP) | 10 Clients(TCP) | UDP | rtt min/avg/max/mdev |
sdn-sw.atla e15/1 <-> rtr.atla:port=xe-0/3/0 | 99.6 Mbits/sec | 100 Mbits/sec | 101 Mbits/sec | 98.0 Mbits/sec | 23.167/23.208/23.279/0.168 ms |
sdn-sw.losa e1/1 <-> rtr.losa:port=et-10/0/0 | 37.1 Mbits/sec | 96.3 Mbits/sec | 97.9 Mbits/sec | 98.0 Mbits/sec | 132.991/133.105/133.380/0.394 ms |
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 |
Stanford InstaGENI AL2S to Missouri InstaGENI AL2S Performance
Collected: 2014-06-17 Endpoints: Missouri InstaGENI Xen VM (iperf client) and Stanford InstaGENI Xen VM (iperf server):
End-points | 1 Client(TCP) | 5 Clients(TCP) | 10 Clients(TCP) | UDP | rtt min/avg/max/mdev |
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 |
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 |
Stanford InstaGENI AL2S to GPO InstaGENI ION Performance
Collected: 2014-06-17 Endpoints: GPO InstaGENI Xen VM (iperf client) and Stanford InstaGENI Xen VM (iperf server) via ATLA cross-connect:
End-points | 1 Client(TCP) | 5 Clients(TCP) | 10 Clients(TCP) | UDP | rtt min/avg/max/mdev |
Stanford IG AL2S to GPO IG ION | 18.9 Mbits/sec | 91.5 Mbits/sec | 98.4 Mbits/sec | 96.5 Mbits/sec | 86.465/86.813/87.109/0.415 ms |
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 |
Please see the GENI Racks Performance page for all performance.