-
Type: Bug
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.8.0, 1.9.0
-
Fix Version/s: 1.10.0
-
Component/s: None
-
Labels:
-
Environment:
commit 382243012ac88b3682e1267d34d8567e48596bc2
-
Story Points:3
-
Epic Link:
-
Sprint:Ibis Sprint 3 - Platform, Junco Sprint #1 - Platform, Junco Sprint #2 - Platform
Change 10673 in gerrit is causing regression of intent throughput test. The results of 3, 5 and 7 node cluster regressed about 50%. Single-node results stay the same (see attachments). NO errors/warnings/exceptions observed in the log.
Update: regression caused by 10673 was fixed by 12296. 12125 is now the cause of a 25% regression.
Steps to reproduce the problem:
1) Start onos cluster with "drivers, null, intentperf" app
2) Configurations:
cfg set org.onosproject.store.flow.impl.DistributedFlowRuleStore backupEnabled true cfg set org.onosproject.net.intent.impl.IntentManager skipReleaseResourcesOnWithdrawal true cfg set org.onosproject.provider.nil.NullProviders deviceCount 30 cfg set org.onosproject.provider.nil.NullProviders topoShape linear cfg set org.onosproject.provider.nil.NullProviders enabled true balance-masters cfg set org.onosproject.intentperf.IntentPerfInstaller numKeys 40000 cfg set org.onosproject.intentperf.IntentPerfInstaller numNeighbors 0 cfg set org.onosproject.intentperf.IntentPerfInstaller cyclePeriod 1000
3) run "intent-perf-start" command from CLI