7 ms·

My preference is TimescaleDB Good "old" Postgre for the win

• GordonS 6y ago
  I've used TimescaleDB with 100 million plus rows, and it's been really fast. It's also been a huge boon to be able to use a single system for both "normal" database stuff as well as time-series.
  • valyala 6y ago
    Did you try VictoriaMetrics for time series data? It easily handles 2 trillion plus rows (20000 times more than TimescaleDB in your setup) on a single node [1]. [1] https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/CaseStudies#adsterra https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/Case...
    • GordonS 6y ago
      No, never even heard of it. There really are a bewildering number of options in this space! I haven't actually tried stressing TimescaleDB, but I imagine it would hold up well if given 50GB of RAM to play with. My point really though, is that TimescaleDB is a great fit for a lot of use cases, with basically no learning curve if you're already au fait with Postgres. And of course if you're already using Postgres elsewhere in your system, it's one less component to manage. I have some industrial IoT use case in mind though, and I'll definitely look more into VictoriaMetrics, so thanks for the tip!