Public bug reported: The _allocate_network method in the ComputeManager is calling _update_resource_tracker but there is no reason to, nothing in that method has changed the instance in a way that will affect how the ResourceTracker manages that instance. This can be costly when you're building several instances at the same time on the same compute because the call to the RT eventually holds a lock which the other instances being built have to contend for.
This is already fixed for Queens with change: https://review.openstack.org/#/c/513473/ This bug is for tracking it for backports. With some internal testing, creating 70 instances on the same compute at the same time, we see about a 22% increase in throughput server create times after this change. ** Affects: nova Importance: Medium Assignee: Matt Riedemann (mriedem) Status: Fix Released ** Affects: nova/ocata Importance: Medium Assignee: Matt Riedemann (mriedem) Status: In Progress ** Affects: nova/pike Importance: Medium Assignee: Matt Riedemann (mriedem) Status: In Progress ** Tags: compute ** Also affects: nova/ocata Importance: Undecided Status: New ** 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/1732316 Title: ComputeManager._allocate_network should not call _update_resource_tracker Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) ocata series: In Progress Status in OpenStack Compute (nova) pike series: In Progress Bug description: The _allocate_network method in the ComputeManager is calling _update_resource_tracker but there is no reason to, nothing in that method has changed the instance in a way that will affect how the ResourceTracker manages that instance. This can be costly when you're building several instances at the same time on the same compute because the call to the RT eventually holds a lock which the other instances being built have to contend for. This is already fixed for Queens with change: https://review.openstack.org/#/c/513473/ This bug is for tracking it for backports. With some internal testing, creating 70 instances on the same compute at the same time, we see about a 22% increase in throughput server create times after this change. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1732316/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp