Hi Liusheng,
We are having the same performance issues and interested in
the following bug ticket.
https://bugs.launchpad.net/ceilometer/+bug/1264434
You said,
> As you said.both the schema level and the code level,the SQL driver in
> Ceilometer should be optimized. thanks for your advicese.
On Mon, 2014-01-06 at 21:06 +0800, 刘胜 wrote:
> Hi jay,Thank you for the comments, I have simply tested the
> performance of ceilometer with mysql driver.,while,the DB table may
> become huge in few days.Unfortunately,the result is not satisfied .
> As you said.both the schema level and the code lev
Hi jay,Thank you for the comments, I have simply tested the performance of
ceilometer with mysql driver.,while,the DB table may become huge in few
days.Unfortunately,the result is not satisfied .
As you said.both the schema level and the code level,the SQL driver in
Ceilometer should be optimize
On 12/28/2013 05:51 AM, 刘胜 wrote:
Hi all：
I have reported a bug about time consuming of “resource-list” in
ceilometer CLI：
https://bugs.launchpad.net/ceilometer/+bug/1264434
In order to Identify the causes of this phenomenon, I have pdb the codes
in my invironment(configured mysql as db driver)
I think the better way is save meters as a field in resource table.
You can look at MongoDB model and may get some ideas.
Beside above, sql backend can introduce Memcache to improve performance.
IMO, the best way may be redesign the sql model to match workload.
On Sat, Dec 28, 2013 at 6:51 PM,
Hi all：
I have reported a bug about time consuming of “resource-list” in ceilometer CLI：
https://bugs.launchpad.net/ceilometer/+bug/1264434
In order to Identify the causes of this phenomenon, I have pdb the codes in my
invironment(configured mysql as db driver):
the most import part of process
