| 2015-04-29 17:14:05 |
Miroslav Anashkin |
description |
Some types of requests to ceilometer in metering dashboard is not optimized. So we have a performance leak in environments with huge amount of ceilometer data.
Main bottlenecks which I see:
* Using a meter-list for getting a "unit" for metric. Meter list get all available metric on environment, it's may be a thousands of records. It's better to use sample-list for this metric with "limit" 1. It gets a 1 sample for metric.
* 7 day period by default for collecting statistics. On huge amount of data it's may freeze the horizon and ceilometer api, it's better to get one day statistics by default. |
Some types of requests to ceilometer in metering dashboard are not optimized. So we have a performance hit in environments with huge amount of ceilometer data.
Main bottlenecks which I see are the following:
* Using a meter-list for getting a "unit" for metric. Meter list gets all available metrics on environment, it may be a thousands of records. It's better to use sample-list for this metric with "limit" 1. It gets only single sample for metric.
* 7 day period by default for collecting statistics. On huge amount of data it may freeze the Horizon and Ceilometer API, it's better to get one day statistics by default. |
|
