Microversion 2.47 punches nova in its special place
Bug #1719966 reported by
Dan Smith
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Dan Smith | ||
Pike |
Fix Committed
|
High
|
Matt Riedemann |
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:
We should...fix that and stuff.
Changed in nova: | |
assignee: | nobody → Dan Smith (danms) |
status: | Confirmed → In Progress |
To post a comment you must log in.
We were always joining on flavor in the database:
https:/ /github. com/openstack/ nova/blob/ 3174ee13a154123 0a4b7b2a4737d67 9691fb14b3/ nova/api/ openstack/ compute/ views/servers. py#L58
And we were always pulling the embedded instance.flavor:
https:/ /github. com/openstack/ nova/blob/ 3174ee13a154123 0a4b7b2a4737d67 9691fb14b3/ nova/api/ openstack/ compute/ views/servers. py#L263
So it would probably be something in here:
https:/ /github. com/openstack/ nova/blob/ 3174ee13a154123 0a4b7b2a4737d67 9691fb14b3/ nova/api/ openstack/ compute/ views/servers. py#L248
Could it be the policy check on all 1000 instances?