| | 4 | |
| | 5 | == Test Methodology == |
| | 6 | |
| | 7 | Test Characteristics: |
| | 8 | - All VMs at one site are on the same VM server, unless otherwise stated. |
| | 9 | - All results are captured for default bandwidth allocation (100Mb/s shaped), unless otherwise stated. |
| | 10 | - All results are captured for default OS (Fedora 15 STD). |
| | 11 | - All results collected between 2013-03-01 through 2013-03-07, unless otherwise stated. |
| | 12 | |
| | 13 | Iperf TCP measurements captured in this page have the following assumptions: |
| | 14 | - All results are for a 60 second test run. |
| | 15 | - for !OpenFlow scenarios, traffic is exchanged to establish data flows before measurement test runs are executed. |
| | 16 | - iperf '1 client' scenario command: 'iperf -c dest_host -t 60' |
| | 17 | - iperf '5 clients' scenario command: 'iperf -c dest_host -t 60 -P 5' |
| | 18 | - iperf '10 clients' scenario command: 'iperf -c dest_host -t 60 -P 10' |
| | 19 | |
| | 20 | Iperf UDP measurements captured in this page have the following assumptions: |
| | 21 | - Each test run is 60 seconds. |
| | 22 | - UDP measurements within a rack requested a bandwidth of 1Gbits/sec for test run |
| | 23 | - UDP measurements between racks requested a bandwidth of 100 Mbits/sec, if results showed that 100Mb/s was possible, then increased to 1Gb/s. |
| | 24 | |
| | 25 | For !OpenFlow scenarios 20 ping packets are exchanged before Iperf is started, this is to have the flows set up not impact iperf measurements. |
| | 26 | |
| | 27 | = Performance Results = |
