Graphite's backend caches incoming data if the disks cannot keep up with the large number of small write operations that occur (each data point is only a few bytes, but most disks cannot do more than a few thousand I/O operations per second, even if they are tiny). Even under heavy load, where the number of metrics coming in each time interval is much greater than the rate at which your storage system can perform I/O operations and lots of data points are being cached in the storage pipeline (see previous question for explanation), Graphite still draws real-time graphs. Graphite will store at most one data point per the finest defined precision (additional data points received will be dropped) in your The aggregator will take in all the metrics and aggregate the data, flushing to Graphite storage in order to match the storage schema.Make you sure, FAN 2.2 is updated and all packages Cent OS.The install script and packages were introduced in 1.4.4.First identify whether the problem is a data collection problem or a data display problem.While it is still functional and fairly reliable, it is very rigid and it really is starting to show its age.I wanted to find a solution that was widely known and supported and if possible – Open Source.
The configuration files (etc/*.conf) contain descriptions of syntax and examples. When installing from source (not from a deb or rpm package), the standalone layout is recommended as it is easier to update than the overlay layout.
From an I/O perspective, under load Graphite performs lots of tiny I/O operations on lots of different files very rapidly.
This is because each distinct metric sent to Graphite is stored in its own database file, similar to how many tools (drraw, Cacti, Centreon, etc) built on top of RRD work.
In fact, Graphite originally did use RRD for storage until fundamental limitations arose that required a new storage engine.
High volume (a few thousand distinct metrics updating minutely) pretty much requires a good RAID array. or is it just fast to process large datasets - we are looking for a simple to use web receiver of packet data to display visually - Graphite seemed like a great solution but now that we have it all configured and running I am guessing we just wasted a lot of time Thanks! retentions = :6h,1min:7d,10min:5y In order to meet your goals you'll need to put an aggregator in front of Graphite.