4 ms·
Looks great! I've just gotten a single instance up and running. Really simple to set up. It seems almost exactly what We've been looking for! Some background:
by babas 10y ago
Looks great! I've just gotten a single instance up and running. Really simple to set up. It seems almost exactly what We've been looking for!
Some background: We have been evaluating different time series databases for use with sensor readings (We probably need to ingest something on the order of 100,000-200,000 samples/s per cluster). The data is from physical sensors like temperature, level, pressure etc. Where all the data is in the form of tag(string)|datetime(ms)|value(decimal).
Have you done any comparisons to other similar software like influxdb, Cassandra, etc? Especially ingestion rate and disk usage.
What kind of pricing can we expect on Managed Hosting?
We are currently leaning towards Influxdb but the cluster licensing stuff they are doing really made us think twice.
- teej 10y agoIf you're looking for recommendations for time series data, this thread still holds up - https://news.ycombinator.com/item?id=8368509 https://news.ycombinator.com/item?id=8368509 I'd consider taking a look at KDB+
- babas 10y agoWe threw kdb+ out of consideration pretty early because it's extremely expensive and we prefer open software.
- mattbillenstein 10y agoInfluxDB doesn't currently handle high-cardinality data sets well -- it needs a lot of RAM.
- babas 10y agoYeah that is one of the biggest issues besides the licensing stuff. But ram is pretty cheap and it seems 200,000 different series/tags fits easily in 32gb.
- etrain 10y agoIf you're willing to try something more bleeding edge: http://btrdb.io/ http://btrdb.io/
- bigger_cheese 10y agoAt my work we use OSI PI which is an Enterprise Historian for storing this kind of physical sensor data - has very good support for time series logging and integrates well with control system(Citect, ABB etc) as well as our LIMS system. It's not free software so that might be a deal breaker for you.