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.
...
We designed a set of experiments to characterize ONOS' latencies, throughput and throughput capacities under various application and network environments. By analyzing the results, we hope to provide network operators and application developers with a "first look" of ONOS’ performance capability. In addition, the performance results should help developers gain insights for identifying performance bottlenecks and optimization opportunities. The following diagram illustrates the key performance evaluation points, viewing ONOS' distributed system as a whole.
...
for 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.
for throughput, D - Intent operations; E - link events (Test deprecated; new test TBD); F - Burst flow rule F - Burst flow rule installation; G - Packet-out (Cbench).
for capacities, E - Topology scaling Operation; H - Max intent installation.
General Experiment Setup:
...
For all experiments except switch and port related related ones, which require Openflow interactions, we implemented in ONOS a set of Null Providers at the Adapter level to interact with the ONOS core. The Null Providers act as device, link, host producers as well as a sink of flow rules. By using the Null Providers, we bypass bypass Openflow adapters and eliminate potential performance limits from having to use real or emulated Openflow devices.
We also instrumented a number of load generators so that we can generate a high-level of loading from the application or the network interfaces to stretch ONOS's performance limits. These generators include:
- Intent an intent performance generator, “onos-app-intent-perf” that interfaces with intent API, and generates self-adjusting intent install and withdraw operations to the highest rate ONOS can sustain;
- a flow rule installer utility python script that interfaces with ONOS flow subsystem to install and remove flow rules in the subsystem;
- a link event (flicker) generator in Null Link providers that sends link up/down descriptions to ONOS core at an elevated rate up to that which ONOS can sustain.
...
- Java HotSpot(TM) 64-Bit Server VM; version 1.8.0_31
- JAVA_OPTS="${JAVA_OPTS:--Xms8G -Xmx8G}"onos-1.1.0 snapshot: commit a31e13471ee626abce2bc43c413fab17586f4fc3
- Additional case-specific ONOS parameters to be described in specific case.
The following Child Pages will describe further setup details, discuss and analyze the results from each test.
Test Plan:
| Test Case | Description | Roadmap | ||||||
|---|---|---|---|---|---|---|---|---|
| SCPFcbench | This is a test of single instance onos Cbench performance with onos fwd app. This test is mainly used for regression monitoring on onos openflow layers. | now | ||||||
| SCPFswitchLat | Measure latencies of switch connect/disconnect as onos cluster scales from 1, to 3, 5, 7 nodes. | now | ||||||
| SCPFportLat | Measure latencies of port connect/disconnect as onos cluster scales from 1, to 3, 5, 7 nodes. | now | ||||||
| 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. | now | ||||||
| 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. | now | ||||||
| SCPFintentEventTp | Measure onos intent operation throughput performance as onos scales | SCPFflowTp1g | Test case to obtain onos flow rule subsystem throughput performance as onos is scaledform 1 to 3, 5, 7 | ,nodes. Also tested in each scale | flow rule, intent "neighboring" scenarios, i.e. when | flow rulesintents are installed only on the local nodes, and all nodes in the cluster. | now | SCPFintentEventTp |
| SCPFscaleTopo | Measure the maximum size of topology that a 3-node onos cluster can discovery and maintain. | now | ||||||
| SCPFflowTp1g | Measure onos flow rule subsystem Test case to obtain onos intent operation throughput performance as onos is scaled scales form 1 to 3, 5, 7 , nodes. Also tested in each scale , intent flow rule "neighboring" scenarios, i.e. when intents flow rules are installed only on the local nodes, and all nodes in the cluster. | now | ||||||
| SCPFcbench | Measure Cbench performance of single-instance onos with fwd app. This test is mainly used for regression monitoring on onos openflow layers. | now | ||||||
| SCPFscalingMaxIntents | Measure the maximum number of intents and corresponding flows that onos can hold as onos scales form 1 | SCPFintentInstallWithdrawLat | Test case to measure latencies of installing and withdrawing intents in a batch size of 1, 100, 100, as onos cluster scales from 1,to 3, 5, 7 nodes. Both cases when FlowObjective intent compiler is on and off are tested. | now | ||||
| SCPFbatchFlowResp | Measure the latencies of flow batch installation and deletion via REST API on a single-instance onos | SCPFintentRerouteLat | Test case to 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. | now | ||||
| SCPFhostLat | Measure latencies of host discovery | SCPFtopologyLat | Test case to measure latencies of network events, specifically switch connect/disconnect, port connect/disconnect, and host discovery, as onos cluster scales from 1, to 3, 5, 7 nodes. | now | SCPFscaleTopo | Test case to establish a big topology, and measure the max topology onos can hold on. | now |