The processing time of ceilometer-expirer is too long when using MySQL backend
Bug #1289166 reported by
Mitsuru Kanabuchi
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Medium
|
gordon chung |
Bug Description
We built an environment of i2 with MySQL backend and we were evaluating it.
And we tried to execute ceilometer-expirer with following datas:
* 5,000 meter objects
* 1,250 resource objects
The elapsed time was 178 secs.
This performance would be a problem in case of a large-scale (or middle-scale) environment.
In my trial calculation, the deletion can't keep up when 20,000 samples registered per pollster's one cycle.
20,000 samples will generated by only 1,000 VMs. It's too small.
I think the ceilometer-expirer needs performance tuning especially in case of using MySQL backend.
Changed in ceilometer: | |
status: | New → Triaged |
Changed in ceilometer: | |
milestone: | none → juno-2 |
Changed in ceilometer: | |
assignee: | gordon chung (chungg) → Eoghan Glynn (eglynn) |
Changed in ceilometer: | |
assignee: | Eoghan Glynn (eglynn) → nobody |
assignee: | nobody → gordon chung (chungg) |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
this is related to the way we delete expired data. we aren't using batch deletes (individually doing it currently)... i believe this will fall inline with our model cleanup... we can't use batch deletes because of a sourceassoc table (which we don't use). we need to clean that table from our model before we can run batch delete.