s.openstack.org>
> Subject: Re: [openstack-dev] [ceilometer]ceilometer-collector high CPU
> usage
>
> >
> > hi,
> Hi Gordon,
>
> >
> > this seems to be similar to a bug we were tracking in earlier[1].
> > basically, any service with a listener neve
Hi all,
Based on my investigation [1], I believe this is a combined effect of
using eventlet and condition variables on Python 2.x. When heartbeats
are enabled in oslo.messaging, you'll see polling with very small
timeout values. This must not waste a lot of CPU time, still it is
kind of annoying.
>
> hi,
Hi Gordon,
>
> this seems to be similar to a bug we were tracking in earlier[1].
> basically, any service with a listener never seemed to idle properly.
>
> based on earlier investigation, we found it relates to the heartbeat
> functionality in oslo.messaging. i'm not entirely sure if i
hi,
this seems to be similar to a bug we were tracking in earlier[1].
basically, any service with a listener never seemed to idle properly.
based on earlier investigation, we found it relates to the heartbeat
functionality in oslo.messaging. i'm not entirely sure if it's because
of it or some
Hi!
Excuse me, if the following question/problem is a basic one, already known
problem,
or even a bad setup on my side.
I just noticed that the most CPU consuming process in an idle
OpenStack cluster is ceilometer-collector. When there are only
10-15 samples/minute, it just constantly eats ab
