← Back to team overview

graphite-dev team mailing list archive

Re: [Question #178969]: Tuning Graphite for 3M points/minute with a single backend machine (a story)

 

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

Ivan Pouzyrevsky posted a new comment:
Cody Stevens has reminded me that I promised a patch. Here it is:
http://cl.ly/3K0317043S2f1M2w1v0Y .

The patch is quite simple: for a given prefix P it forbids to perform an
update for a metric M with prefix P if the queue size is less than N
points. P and N are parameters. The consequences of such behaviour are
the following: firstly, it increases average I/O request size (hence
increasing the throughput); secondly, it increases memory footprint
since from now on you have to store way more datapoints in memory. In my
current setup I have total memory consumption by carbon-caches about
17.4G with 1.74G per instasnce. Total cache size oscillates between 20M
and 110M points with 2M to 11M points per instance.

I hope that someone find this patch useful or use it for further
improvements in writer's algorithm.

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