yahoo-eng-team team mailing list archive

[Ryan Moats <rmoats@xxxxxxxxxx>]

Public bug reported:

Create 100 tenants each one with the following setup where each router
is scheduled to the same legacy node that has the L3 agent configured to
use the native OVSDB inerface.

tenant network ------- router ------ external network

Reference http://ibin.co/2GuI6plJvngR for graph of performance during set up of 100 routers.
In the above graph, y-axis is time in seconds, and x-axis is pass through _ovs_add_port (two per router add).

DbSetCommand's performance increases with each router add.  To support
scale, this needs to be closer to O(1) and perform significantly better
than using ovs-vsctl via rootwrap daemon.

** Affects: neutron
     Importance: Medium
         Status: New


** Tags: kilo-backport-potential liberty-rc-potential performance

** Changed in: neutron
   Importance: High => Medium

** Tags added: kilo-backport-potential liberty-rc-potential

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1499893

Title:
  Native OVSDB DbSetCommand shows O(n) performance

Status in neutron:
  New

Bug description:
  Create 100 tenants each one with the following setup where each router
  is scheduled to the same legacy node that has the L3 agent configured
  to use the native OVSDB inerface.

  tenant network ------- router ------ external network

  Reference http://ibin.co/2GuI6plJvngR for graph of performance during set up of 100 routers.
  In the above graph, y-axis is time in seconds, and x-axis is pass through _ovs_add_port (two per router add).

  DbSetCommand's performance increases with each router add.  To support
  scale, this needs to be closer to O(1) and perform significantly
  better than using ovs-vsctl via rootwrap daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1499893/+subscriptions