nova performance regression
Bug #1227362 reported by
Aaron Rosen
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Pádraig Brady |
Bug Description
I was benchmarking the lastest code and noticed that nova on master takes a significantly more amount of time for an instance to go from spawning -> ACTIVE then compared to grizzly almost 20Times more.
I'm filing this bug just to track the issue as I try to figure out what is causing the regression.
testing using: nova boot --image cirros-
on havana vs grizzly.
Changed in nova: | |
assignee: | nobody → Aaron Rosen (arosen) |
importance: | Undecided → High |
importance: | High → Undecided |
Changed in nova: | |
assignee: | Aaron Rosen (arosen) → Pádraig Brady (p-draigbrady) |
status: | New → Triaged |
Changed in nova: | |
milestone: | none → havana-rc1 |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-rc1 → 2013.2 |
To post a comment you must log in.
I can confirm that this issue was introduced sometime between master and 566a44fbdf25160 63f34598ba167a4 582b90fdac .
Using: 566a44fbdf25160 63f34598ba167a4 582b90fdac there is no regression.