Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
The performance evaluation points indicated in the diagram include: for latencies,
Latencies:
- A - Switch
...
- Connect/
...
- Disconnect
- B - Link
...
- Up/
...
- Down
- C - Intent Batch Install/Withdraw/Re-
...
- Route
- I - Flow
...
- Batch Installation from REST API
...
- L - Host
...
- Add
- M - Mastership Failover
Throughput:
...
- D - Intent
...
- Operations
- F - Burst
...
- Flow Rule Installation
- G - Flow-
...
- Mod (Cbench)
Capacities.for capacities,
- E - Topology
...
- Scaling Operation
...
- H - Max
...
- Intent Installation
General Experiment Setup:
...
The following child pages describe further setup details, discuss and analyze the results from each test:
Test Plan:
| Test | Description | Test Plan Article |
|---|---|---|
| SCPFswitchLat | Measure latencies of switch connect/disconnect as onos cluster scales from 1, to 3, 5, 7 nodes. | Experiment A&B Plan - Topology (Switch, Link) Event Latency |
| SCPFportLat | Measure latencies of port connect/disconnect as onos cluster scales from 1, to 3, 5, 7 nodes. | Experiment A&B Plan - Topology (Switch, Link) Event Latency |
| SCPFintentInstallWithdrawLat | Measure latencies of installing and withdrawing intents in a batch size of 1, 100, 1000, as onos cluster scales from 1, to 3, 5, 7 nodes. Both cases when FlowObjective intent compiler is on and off are tested. | Experiment C Plan - Intent Install/Remove/Re-route Latency |
| SCPFintentRerouteLat | Measure latencies of installed intents being rerouted, in an event of network path change, when onos cluster scales from 1 to 3, 5, 7 nodes. Both cases when FlowObjective intent compiler is on and off are tested. | Experiment C Plan - Intent Install/Remove/Re-route Latency |
| SCPFintentEventTp | Measure onos intent operation throughput performance as onos scales form 1 to 3, 5, 7 nodes. Also tested in each scale, intent "neighboring" scenarios, i.e. when intents are installed only on the local nodes, and all nodes in the cluster. | Experiment D Plan - Intents Operations Throughput |
| SCPFscaleTopo | Measure the maximum size of topology that a 3-node onos cluster can discover and maintain. | Experiment E Plan - Topology Scaling Operation |
| SCPFflowTp1g | Measure onos flow rule subsystem throughput performance as onos scales form 1 to 3, 5, 7 nodes. Also tested in each scale flow rule "neighboring" scenarios, i.e. when flow rules are installed only on the local nodes, and all nodes in the cluster. | Experiment F Plan - Flow Subsystem Burst Throughput |
| SCPFcbench | Measure Cbench performance of single-instance onos with fwd app. This test is mainly used for regression monitoring on onos openflow layers. | Experiment G Plan - Single-node ONOS Cbench |
| SCPFscalingMaxIntents | Measure the maximum number of intents and corresponding flows that onos can hold as onos scales form 1 to 3, 5, 7 nodes. Both cases when FlowObjective intent compiler is on and off are tested. | Experiment H Plan - Max Intent Installation and ReRoute |
| SCPFbatchFlowResp | Measure the latencies of flow batch installation and deletion via REST API on a single-instance onos. | Experiment I Plan - Single Bench Flow Latency Test |
| SCPFhostLat | Measure latencies of host discovery as onos cluster scales from 1, to 3, 5, 7 nodes. | Experiment L Plan - Host Add Latency |
| SCPFmastershipFailoverLat | Masure the latencies of ONOS node recovery as ONOS cluster scales from 3, to 5, 7 nodes. | Experiment M Plan - Mastership Failover Latency |