Experiment Measurements
This page captures status and execution details for the Experiment Measurements. For overall status see the GENI Network Stitching Test Status page and for test details see the GENI Network Stitching Test Plan page.
Last update: 06/11/13
Measurements | State | Ticket | Comments
|
GNS-T1 - Topology 1 - Utah InstaGENI to GPO InstaGENI | | |
|
GNS-T2 - Topology 2 - InstaGENI Utah to GPO ExoGENI | | |
|
GNS-T3 - Topology 3 - InstaGENI Utah to GPO ExoGENI to LONI and MAX | | |
|
GNS-T4 - Topology 4 - InstaGENI Utah to GPO ExoGENI to CENIC | | |
|
GNS-T5 - Topology 5 - InstaGENI Utah to GPO ExoGENI to NYSERNet | | |
|
GNS-T6 - Topology 6 - Utah PG to GPO InstaGENI | | |
|
Test Execution
Assumptions:
- pgeni.gpolab.bbn.com or GENI Portal credential are used for tests in this page.
- Some end-points exist in multiple test cases, so their measurements will be not be duplicated.
Notes:
- Stitcher currently does not support AM API v3, is delivered to run AM API V2.
- Capacity must be specified for scenarios where Utah IG is end-point.
Measurements Goals
The set of GENI Network Stitching (GNS) test topologies selected to validate stitching experiment scenarios are also used to benchmark measurements to characterize various areas including setup timing, tear down timing, timing for an experiment to change data paths from one stitched VLAN to another, end-host to end-host data flow set up timing and delay. Throughput will also be measured with iperf between endpoint hosts using the following methodology:
- All results are captured for default bandwidth allocation, unless otherwise stated.
- All results are for a 60 second test runs.
- TCP iperf measurements are collected for:
- '1 client' scenario using command: 'iperf -c dest_host -t 60'
- '5 clients' scenario using command: 'iperf -c dest_host -t 60 -P 5'
- '10 clients' scenario command: 'iperf -c dest_host -t 60 -P 10'
- UDP iperf measurements are run for 10 seconds increments to determine bandwidth supported
Measurements Collected
This sections captures all measurements collected for the Network Stitching test effort.
GNS-T1 - Topology 1 - Utah InstaGENI to GPO InstaGENI
Description | Results Collected
|
VLAN stitching setup timing |
|
VLAN stitching tear down timing |
|
Data path change from stitched VLAN to another |
|
End-host to end-host data flow set up timing |
|
End-host to end-host delay |
|
Throughput between end-hosts |
|
GNS-T2 - Topology 2 - InstaGENI Utah to GPO ExoGENI
Description | Results Collected
|
VLAN stitching setup timing |
|
VLAN stitching tear down timing |
|
Data path change from stitched VLAN to another |
|
End-host to end-host data flow set up timing |
|
End-host to end-host delay |
|
Throughput between end-hosts |
|
GNS-T3 - Topology 3 - InstaGENI Utah to GPO ExoGENI to LONI and MAX
Description | Results Collected
|
VLAN stitching setup timing |
|
VLAN stitching tear down timing |
|
Data path change from stitched VLAN to another |
|
End-host to end-host data flow set up timing |
|
End-host to end-host delay |
|
Throughput between end-hosts |
|
GNS-T4 - Topology 4 - InstaGENI Utah to GPO ExoGENI to CENIC
Description | Results Collected
|
VLAN stitching setup timing |
|
VLAN stitching tear down timing |
|
Data path change from stitched VLAN to another |
|
End-host to end-host data flow set up timing |
|
End-host to end-host delay |
|
Throughput between end-hosts |
|
GNS-T5 - Topology 5 - InstaGENI Utah to GPO ExoGENI to NYSERNet
Description | Results Collected
|
VLAN stitching setup timing |
|
VLAN stitching tear down timing |
|
Data path change from stitched VLAN to another |
|
End-host to end-host data flow set up timing |
|
End-host to end-host delay |
|
Throughput between end-hosts |
|
GNS-T6 - Topology 6 - Utah PG to GPO InstaGENI
Description | Results Collected
|
VLAN stitching setup timing |
|
VLAN stitching tear down timing |
|
Data path change from stitched VLAN to another |
|
End-host to end-host data flow set up timing |
|
End-host to end-host delay |
|
Throughput between end-hosts |
|