Scheduler, performance impact when dealing with aggregates
Bug #1300775 reported by
Sahid Orentino
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Medium
|
Unassigned |
Bug Description
During a scheduling if we use filter that needs to get data from aggregates like CoreFilterAggre
The filter retrieves metadata from the database for every host and can creates a performance impact if we have several hosts.
Changed in nova: | |
assignee: | nobody → sahid (sahid-ferdjaoui) |
description: | updated |
tags: | added: scheduler |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
assignee: | sahid (sahid-ferdjaoui) → nobody |
Changed in nova: | |
status: | Triaged → Confirmed |
To post a comment you must log in.
Ideally lets fix this in a way that means that caching scheduler would cache this DB query.
So that probably means put it inside the host_manager, but see how that looks, it might be the wrong place/too deep