yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

We were always joining on flavor in the database:

https://github.com/openstack/nova/blob/3174ee13a1541230a4b7b2a4737d679691fb14b3/nova/api/openstack/compute/views/servers.py#L58

And we were always pulling the embedded instance.flavor:

https://github.com/openstack/nova/blob/3174ee13a1541230a4b7b2a4737d679691fb14b3/nova/api/openstack/compute/views/servers.py#L263

So it would probably be something in here:

https://github.com/openstack/nova/blob/3174ee13a1541230a4b7b2a4737d679691fb14b3/nova/api/openstack/compute/views/servers.py#L248

Could it be the policy check on all 1000 instances?

** Tags added: api performance

** Changed in: nova
       Status: New => Confirmed

** Changed in: nova
   Importance: Undecided => High

** Also affects: nova/pike
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1719966

Title:
  Microversion 2.47 punches nova in its special place

Status in OpenStack Compute (nova):
  Confirmed
Status in OpenStack Compute (nova) pike series:
  New

Bug description:
  Testing with 500 instances in ACTIVE, and 500 in ERROR state, using
  curl to pull all 1000 instances ten times in a row, 2.47 clearly shows
  a knee in the curve on average response time:

  https://imgur.com/a/2lmiw

  We should...fix that and stuff.

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