yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

Per similar bugs I've found in here, performance improvements are really
hard to track as bugs because they are a point in time behavior that
doesn't really have a repeat scenario. We should take a push on specs
for performance improvements. I think we all know that large numbers of
API calls take a while, but what's acceptable is still up for debate.

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

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

-- 
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/1359808

Title:
  extended_volumes slows down the nova instance list by 40..50%

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  When listing ~4096 instances, the nova API (n-api) service has high CPU(100%)  usage because it does individual SELECTs,
  for every server's block_device_mapping. This adds ~20-25 sec to the response time.

  Please use more efficient way for getting the block_device_mapping,
  when multiple instance queried.

  This line initiating the individual select:
  https://github.com/openstack/nova/blob/4b414adce745c07fbf2003ec25a5e554e634c8b7/nova/api/openstack/compute/contrib/extended_volumes.py#L32

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