yahoo-eng-team team mailing list archive

[Max <2037107@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In our environment we have an external network with few subnets(20). We
use network rbacs to restrict access to it. Currently we have
networkrbacs for around 2500 projects for that network.

We noticed that the neutron api needs about 25 seconds for a POST request
to the /v2.0/floatingips endpoint. We traced it down to the neutron
find_candidate_subnets() method. Here sqlalchemy needs 14 seconds to
parse ~50000 results into subnet objects.

We use the latest stable/yoga version.
I attached the mysql query and the neutron profiling for the neutron.db.ipam_backend_mixin._ipam_get_subnets method(14sec).

** Affects: neutron
     Importance: Undecided
         Status: New

** Attachment added: "sqlquery_and_neutron-profiling.txt"
   https://bugs.launchpad.net/bugs/2037107/+attachment/5703572/+files/sqlquery_and_neutron-profiling.txt

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

Title:
  slow port creation with a large amount of networkrbacs

Status in neutron:
  New

Bug description:
  In our environment we have an external network with few subnets(20). We
  use network rbacs to restrict access to it. Currently we have
  networkrbacs for around 2500 projects for that network.

  We noticed that the neutron api needs about 25 seconds for a POST request
  to the /v2.0/floatingips endpoint. We traced it down to the neutron
  find_candidate_subnets() method. Here sqlalchemy needs 14 seconds to
  parse ~50000 results into subnet objects.

  We use the latest stable/yoga version.
  I attached the mysql query and the neutron profiling for the neutron.db.ipam_backend_mixin._ipam_get_subnets method(14sec).

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