graphite-dev team mailing list archive

[chrismd <question172048@xxxxxxxxxxxxxxxxxxxxx>]

Question #172048 on Graphite changed:
https://answers.launchpad.net/graphite/+question/172048

chrismd proposed the following answer:
There isn't a hard and fast limit, it depends on a lot of factors. Since
graphite stores datapoints for each metric in its own file, a glob that
matches 500 metrics means graphite has to read from 500 files, which is
quite expensive. If you use aggregate graphs frequently (ie.
sumSeries(lots.of.metrics.*)) then the best thing to do is to precompute
the aggregate value so it gets stored as its own metric, and thus
rendering that same graph will involve only 1 file and thus be very
fast. You can use the carbon-aggregator daemon to compute aggregates for
you so you don't have to modify your clients, check out the example
aggregation-rules.conf.

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.