5 ms·
Slightly off-topic perhaps. For my use case (both short-term and long-term storage of sensors and metrics of a small Home Assistant instance) it probably doesn'
by orphea 1y ago
Slightly off-topic perhaps. For my use case (both short-term and long-term storage of sensors and metrics of a small Home Assistant instance) it probably doesn't matter, but what could someone recommend? ClickHouse looks kind of neat and it doesn't appear to be difficult to admin.
- ejs 1y agoSince this is a timescaleDB topic, would timescale not work? (With a basic DB and a few continuous aggregates running in the background?)
- skowalak 1y agoAt the company I work at we manage a lot of historical data with Timescale, but we have also had good results with vanilla PostgreSQL for smaller time-series-data-sets. If you are already comfortable with Postgres this might be worth a look.
- suyash 1y agoI would go with InfluxDB, actually it's powers several Home Assistant apps behind the scene already for a reason.
- suyash 1y agobtw I work at InfluxData and happy to answer any question, just ask here or reach our in our forums
- Rebelgecko 1y agoIf you like standard SQL-y type queries, timescaledv itself is a good option. Influx is another option but it has a steeper learning curve and imo it doesn't pay off