graphite-dev team mailing list archive

[Nicholas Leskiw <question220485@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

Nicholas Leskiw proposed the following answer:
Graphite tries to write data in bursts to the disk.  This is due to the
nature of spinning disks. Writing sequential data to disk is not much
more expensive than writing a single datapoint; most of the time is
wasted in the seek.  This is why graphite pre-allocates data to disk, to
make it as sequential as possible.  Then data queues up and many data
points are written at once.

Read this question about tuning your carbon cache to use your disk most
effectively:

https://answers.launchpad.net/graphite/+question/212303

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