[openstack-dev] [gnocchi] Redis for storage backend
heut2008 at gmail.com
Wed Oct 18 16:15:58 UTC 2017
We launched 300vms and each vm has about 10 metrics, OpenStack cluster have
3 controllers and 2 compute nodes(ceph replication is set to 2).
what we want to archive is to make all metric measures data get processed
as soon as possible, metric processing delay is set to 10s, and ceilometer
polling interval is 30s.
when the backend of incoming and storeage is set to ceph, the average of
shows that there are around 7000 measures waiting to be process, but when
changing incoming and storage backend to Redis, the result of gnocchi
status shows unprocessed measures is around 200.
we try to add more metricd process on every controller nodes, to improve
the performance of
calculate and writing speed to storage backend but have little effect.
On Fri, Oct 13, 2017 at 9:03 PM, gordon chung <gord at live.ca> wrote:
> On 2017-10-13 03:37 AM, Julien Danjou wrote:
> > On Fri, Oct 13 2017, Yaguang Tang wrote:
> >> I see the latest Gnocchi support using Redis as a storage backend, I am
> >> testing performance of Redis and Ceph, it seems using Redis as storage
> >> backend we can achieve more realtime metric
> >> data, gnocchi status shows there is always few metric to process.
> >> Is Redis a recommend storage backend ?
> > Redis is recommended as an incoming measures backend, not really as a
> > storage – though it really depends on the size of your installation.
> > Up until 4.0 version, Gnocchi process metrics every
> > $metricd.metric_processing_delay seconds. With version 4.1 (to be
> > released), the Redis incoming driver has a more realtime processing
> > delay which avoids having to poll for incoming data.
> what Julien said :)
> redis as a storage driver really depends on how you setup persistence
> and how much you trust it.
> would love to see your redis vs ceph numbers compared to mine :)
>  https://redis.io/topics/persistence
>  https://aphyr.com/posts/283-jepsen-redis
>  https://firstname.lastname@example.org/gnocchi-4-introspective-a83055e99776
> (tested part of 4.1 optimisations)
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev