graphite-dev team mailing list archive

[Brett Riotto <question212303@xxxxxxxxxxxxxxxxxxxxx>]

New question #212303 on Graphite:
https://answers.launchpad.net/graphite/+question/212303

We have a graphite server up and running that is currently hosting 6000 metrics at 20 second granularity. The hardware on this server is nothing to brag about. The iowait on this node is averaging above 30 seconds. Something needs to be done to reduce the rate that we are writing from the 300/sec range to the 70/sec range.
There are a couple of things that we have looked at/considered:
1. We would like to reduce our granularity to minutely data, which from testing on a vm, I think this requires us to use the whisper-resize.py . We would have to do this for 6000 metrics however, and we are not sure what the best way to go about this is. I've read that there may be a whisper-multi-resize.py, but I'm not sure where to get that or if it will run with python 2.4 . Is there a easier way to change the granularity without losing historical data?

2. I have read a little about queuing metrics for writes, I.e. Waiting for 3 data points to accumulate before you       perform the I/O. Is there a way to configure this?

3. Is there another solution that we are overlooking? Is there a solid wait to optimize the I/O? Would changing the carbon.conf MAX_UPDATES_PER_SECOND or any other setting help?

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