← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1497396] [NEW] Network creation and Router Creation times degrade with large number of instances

 

Public bug reported:

We are trying to analyze why creation of routers and networks degrades
when there is a large number of instances of these. Running cprofile on
the L3 agent indicated that ensure_namespace function seems to degrade
when a large number of namespaces are present.

Looking through the code all the namespaces are listed with the "ip
netns list" command and then compared against the one that is of
interest. This scales badly since with large number if instances the
number of comparisons increases.

An alternate way to achieve the same result could be to check for the
desired namespace ("ls /var/run/netns/qrouter-<id>") or to run a command
(maybe the date commands?)  and check the response.

Either method described above would have a constant time for execution,
rather than the linear time as seen presently.

Thanks,
-Uday

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Network creation and Router Creation times degrade with large number
  of instances

Status in neutron:
  New

Bug description:
  We are trying to analyze why creation of routers and networks degrades
  when there is a large number of instances of these. Running cprofile
  on the L3 agent indicated that ensure_namespace function seems to
  degrade when a large number of namespaces are present.

  Looking through the code all the namespaces are listed with the "ip
  netns list" command and then compared against the one that is of
  interest. This scales badly since with large number if instances the
  number of comparisons increases.

  An alternate way to achieve the same result could be to check for the
  desired namespace ("ls /var/run/netns/qrouter-<id>") or to run a
  command (maybe the date commands?)  and check the response.

  Either method described above would have a constant time for
  execution, rather than the linear time as seen presently.

  Thanks,
  -Uday

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


Follow ups