https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OVSDB-364 ovsdb <p>The performance of the OVSDB Southbound Plugin to process Update Notification from Open vSwitch is really slow. One of reasons of the bad performance is that the plugin does a lot of unnecessary read operations on MD-SAL. The run() method of the TransactionInvokerImpl class calls a lot of the unnecessary read operations. This has a lot of bad impact, especially when we run several OpenDaylight nodes as a cluster in which an OpenDaylight node sometimes needs to communicate with another node (shard leader) to get data during the read operation.</p> <p>We are thinking this bad performance probably causes the <a href="https://jira.opendaylight.org/browse/NETVIRT-5" title="Instances in Compute node not able to reach dhcp" class="issue-link" data-issue-key="NETVIRT-5"><del>NETVIRT-5</del></a> which is a critical bug for NetVirt.<br/> Therefore, we need to fix this problem. Especially, in this bug report, I would like to focus on removing the unnecessary read operations during processing Update Notification.</p> <p>Operating System: All<br/> Platform: All</p> OVSDB-364

A tons of unnecessary read operations in the switch update processing control flow

Bug Resolved Done Unassigned Hideyuki Tai Fri, 19 Aug 2016 03:14:52 +0000 Thu, 19 Oct 2017 21:26:58 +0000 Tue, 23 Aug 2016 15:06:41 +0000 unspecified Southbound.Open_vSwitch 0 2 <p>I think the master, stable/boron, and stable/beryllium branches have this issue.</p> <p>I've noticed the OVSDB Southbound Plugin ALWAYS calls SouthboundUtil.readNode() SEVERAL TIMES on processing ONE Update Notification regardless on the contents of the Update Notification.<br/> That's because some classes which extends AbstractTransactionCommand always call SouthboundUtil.readNode() in any conditions.</p> <p>For example, please check the OvsdbQueueRemovedCommand.java.</p> <p> <span class="error">&#91;OvsdbQueueRemovedCommand.java&#93;</span></p> <p> 49 @Override<br/> 50 public void execute(ReadWriteTransaction transaction) {<br/> 51 final InstanceIdentifier&lt;Node&gt; nodeIId = getOvsdbConnectionInstance().getInstanceIdentifier();<br/> 52 final Optional&lt;Node&gt; ovsdbNode = SouthboundUtil.readNode(transaction, nodeIId);<br/> 53 if (ovsdbNode.isPresent()) {</p> <p>Here, this execute() method calls the SouthboundUtil.readNode() method without any condition check.</p> <p>However, I think this method doesn't need the node information when it doesn't have any data to process, so this method should check condition first as follows.</p> <p> <span class="error">&#91;OvsdbQueueRemovedCommand.java (Modification proposed)&#93;</span></p> <p> 47 @Override<br/> 48 public void execute(ReadWriteTransaction transaction) {<br/> 49 if (removedQueueRows == null || removedQueueRows.isEmpty() ) </p> { 50 return 51 } <p> 52<br/> 53 final InstanceIdentifier&lt;Node&gt; nodeIId = getOvsdbConnectionInstance().getInstanceIdentifier();<br/> 54 final Optional&lt;Node&gt; ovsdbNode = SouthboundUtil.readNode(transaction, nodeIId);</p> <p>Please note that every time run() method of the TransactionInvokerImpl class calls execute() method of OvsdbOperationalCommandAggregator class, execute() method of OvsdbQueueRemovedCommand class is always called by OvsdbOperationalCommandAggregator class.<br/> I mean the OVSDB Southbound Plugin ALWAYS calls the exeucte() of the OvsdbQueueRemovedCommand class and calls the SouthboundUtil.readNode() every time the plugin receives Update Notification from Open vSwitch regardless on the contents of the Update Notification, even if Update Notification doesn't have any updates regarding to Queue table.</p> <p>I'm writing a patch for this.<br/> <a href="https://git.opendaylight.org/gerrit/#/c/44374/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/44374/</a><br/> I plan to modify other classes which extends AbstractTransactionCommand in the above patch.</p> <p>To make it easy for users to know the performance issue happens due to Update Notification from OVS, I've pushed a patch to log events regarding to the performance issue.<br/> <a href="https://git.opendaylight.org/gerrit/#/c/44520/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/44520/</a></p> <p>And, the log messages which the above patch introduces also helps developers to improve the scalability, and identify the root cause of issues such as <a href="https://jira.opendaylight.org/browse/NETVIRT-5" title="Instances in Compute node not able to reach dhcp" class="issue-link" data-issue-key="NETVIRT-5"><del>NETVIRT-5</del></a>.</p> <p>There are patches which removed unnecessary read operations:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/44526/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/44526/</a> (master)<br/> <a href="https://git.opendaylight.org/gerrit/#/c/44374/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/44374/</a> (stable/boron)<br/> <a href="https://git.opendaylight.org/gerrit/#/c/44525/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/44525/</a> (stable/beryllium)</p> Development External issue ID 6475 External issue URL Rank 0|i0229z: