Any idea on the performance of InfluxDB, I want to log ~500GB per hour in a timeseries DB. Can influx DB handle that?
The upcoming release should be able to handle that kind of load. I wrote a bit about what's coming here:
http://influxdb.com/blog/2014/12/08/clustering_tags_and_enha...
Re:Graph everything with Graphite
by gingerlime on Friday December 12, 2014 @10:14AM
(#8740401)
any idea what happened to the project that resulted in this halt?
It was originally written and open sourced by Chris Davis of Orbitz. Presumably he either moved on to a new job, got bored with it, or it met his original design goals so he didn't feel the need to completely rewrite the backend just because the internet asked him to.
Re:Graph everything with Graphite
by gingerlime on Saturday December 13, 2014 @03:55AM
(#8744652)
Surprising that with quite a few core contributors and (as far as I'm aware) pretty good adoption nobody picked it up though...
Development of graphite is effectively dead. The datastore component (carbon and whisper) has design issues, and the official replacement (ceres) hasn't seen any commits this year. There are a some alternatives, though.
For data storage Cyanite [0] speaks the graphite protocol and stores the data in Cassandra. Alternately, InfluxDB [1] speaks the graphite protocol and stores the data in itself
To get the data back out, there's graphite-api [2] which can be hooked up to cyanite [3] or influxdb [4]. You can then connect any graphite dashboard you like, such as grafana [5], to it.
[0] https://github.com/pyr/cyanite [1] http://influxdb.com [2] https://github.com/brutasse/graphite-api [3] https://github.com/brutasse/graphite-cyanite [4] https://github.com/vimeo/graphite-influxdb [5] http://grafana.org