glance backend is in crazy resize when an image is uploading
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
In Progress
|
Medium
|
Liang Fang | ||
Glance |
New
|
Undecided
|
Unassigned | ||
glance_store |
In Progress
|
High
|
Erno Kuvaja |
Bug Description
When uploading a volume to glance as an image, the glance server don't know the image size, so the backend storage server(such as ceph) need to resize the image every time it received new chunk of data(by default 64K). So there will be huge times of resize operations that will impact the performance.
- regarding cinder, it has not calculate the image size and pass the correct size to glance
- regarding glance, it should allow the client to set image size.
This is an known issue which can be found in driver files of all kinds of backend storage system:
In file: glance_
In file: glance_
In file: glance_
In all these files, there're comments like below:
# If the image size provided is zero we need to do
# a resize for the amount we are writing. This will
# be slower so setting a higher chunk size may
# speed things up a bit.
Changed in cinder: | |
assignee: | nobody → Liang Fang (liangfang) |
Changed in glance: | |
assignee: | nobody → Liang Fang (liangfang) |
Changed in python-glanceclient: | |
assignee: | nobody → Liang Fang (liangfang) |
Changed in cinder: | |
status: | Incomplete → In Progress |
Changed in glance: | |
status: | New → In Progress |
Changed in python-glanceclient: | |
status: | New → In Progress |
Changed in cinder: | |
importance: | Undecided → Medium |
no longer affects: | python-glanceclient |
description: | updated |
Changed in glance-store: | |
assignee: | nobody → Erno Kuvaja (jokke) |
status: | New → Triaged |
What is the Cinder issue here?