The performance of volume index is low
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Fix Released
|
Medium
|
wangxiyuan | ||
Bug Description
Now, when get the volume without limit, cinder will get all volume information from db first. Then get the max limit from CONF and filter it. It will waste much time to do it.
For example, if cinder has more than ten thousand volumes and max limit is one thousand. Cinder will get the ten thousand ones, then filter it. The remaining nine thousand volume is useless but have already occupied memory and time.
So I think a better way is to get the one thousand volume directly from db.
offset could be passed to db layer as well. Do indexing only once in db in enough and efficient.
Here are some test data:
Env: There are 60,000 volumes items, 370,000 volume_metadata items and
240,000 volume_
Old volume index will use nearly 10G memory.
The new one just use about 500M memory.
| Changed in cinder: | |
| assignee: | nobody → wangxiyuan (wangxiyuan) |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to cinder (master) | #1 |
| Changed in cinder: | |
| status: | New → In Progress |
| description: | updated |
| description: | updated |
| John Griffith (john-griffith) wrote | #2 |
| OpenStack Infra (hudson-openstack) wrote | #3 |
| Changed in cinder: | |
| assignee: | wangxiyuan (wangxiyuan) → Gorka Eguileor (gorka) |
| Changed in cinder: | |
| assignee: | Gorka Eguileor (gorka) → wangxiyuan (wangxiyuan) |
| Xing Yang (xing-yang) wrote | #4 |
| Changed in cinder: | |
| milestone: | none → liberty-3 |
| importance: | Undecided → Medium |
| OpenStack Infra (hudson-openstack) wrote Change abandoned on cinder (master) | #5 |
| wangxiyuan (wangxiyuan) wrote | #6 |
| Changed in cinder: | |
| status: | In Progress → Fix Committed |
| Changed in cinder: | |
| status: | Fix Committed → Fix Released |
| Changed in cinder: | |
| milestone: | liberty-3 → 7.0.0 |
Fix proposed to branch: master
Review: https:/