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.

Have questions? Stuck? Please check our FAQ for some common questions and answers.

2.2: Experiment A&B - Topology (Switch, Link) Event Latency

Created by Jenkins Technical User, last modified on Aug 14, 2019

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

System Env:

Server: Dual XeonE5-2670 v2 2.5GHz; 64GB DDR3; 512GB SSD
System clock precision is +/- 1 ms
1Gbps NIC
JAVA_OPTS="${JAVA_OPTS:--Xms8G -Xmx8G}"

ONOS Apps:

drivers
metrics
openflow

ONOS Config:

cfg set org.onosproject.net.topology.impl.DefaultTopologyProvider maxEvents 1
cfg set org.onosproject.net.topology.impl.DefaultTopologyProvider maxBatchMs 0
cfg set org.onosproject.net.topology.impl.DefaultTopologyProvider maxIdleMs 0

Test Procedure:

Switch event generate on ONOS1 by connecting ovs switch to it.
Record tshark (tcp syn-ack) and graph event timestamp to calculate differences.

Note: Error bars in the graphs below represent standard deviations. Only the upper error bars are shown.

No labels