3 ms·

Thanks for the comments. I (not the author, but a co-worker) mentioned in another comment that we are working on more benchmarks that we hope to share soon, par

Thanks for the comments. I (not the author, but a co-worker) mentioned in another comment that we are working on more benchmarks that we hope to share soon, particularly in regards to read performance. We've seen some impressive speed-ups for aggregates grouped by time intervals, but we're still a bit early in our tuning on the query optimizations to give out more numbers. Again, hopefully in the next few weeks. Space requirements can admittedly be a bit higher than some other time-series databases or column stores. Since disk is cheaper than memory, and with easy ways of doing retention, we think its a worthwhile trade-off for people for now. But compression is something we will look to down the road. For our later benchmarks we will include memory/space comparisions to help people evaluate. As for node splitting, our clustering solution (not yet released) is being worked on quite a bit as well. When its closer to being ready we'll include our thoughts on how to best manage your partitions.

Dangeranger 10y ago
Are you considering configurable automated downsampling triggers for inserts over time buckets? Essentially these would be aggregates triggered to fire and insert the resulting values into another table of lower granularity after the time bucket has closed (1s, 10s, 1m, 5m, etc.)
- cevian 10y ago
  This is a great usage idea and something that should be fairly easy once we support close and update triggers (on our list of todos)
- mfreed 10y ago
  And just to follow-on previous comment: Yes, we plan to offer such continuous aggregations, where data of lower granularity can then just be automatically written into a different hypertable. This also plays nicely with configurable data retention policies if desired, e.g., only store raw data for X days, but more aggregated data for longer periods of time.
buremba 10y ago
I will be waiting for you to release your clustering solution. Will it be also included in the open-source version or are you planning to release it as part of your commercial service?
- RobAtticus 10y ago
  Clustering will be in the open-source version.
  - buremba 10y ago
    Great, thanks!

Dangeranger 10y ago

Are you considering configurable automated downsampling triggers for inserts over time buckets? Essentially these would be aggregates triggered to fire and insert the resulting values into another table of lower granularity after the time bucket has closed (1s, 10s, 1m, 5m, etc.)

cevian 10y ago
This is a great usage idea and something that should be fairly easy once we support close and update triggers (on our list of todos)
mfreed 10y ago
And just to follow-on previous comment: Yes, we plan to offer such continuous aggregations, where data of lower granularity can then just be automatically written into a different hypertable. This also plays nicely with configurable data retention policies if desired, e.g., only store raw data for X days, but more aggregated data for longer periods of time.

buremba 10y ago

I will be waiting for you to release your clustering solution. Will it be also included in the open-source version or are you planning to release it as part of your commercial service?

RobAtticus 10y ago
Clustering will be in the open-source version.
- buremba 10y ago
  Great, thanks!