3 ms·
If you need to store 15GB of sensor data, a MySQL derivate is not what I'd choose
by theshrike79 2y ago
If you need to store 15GB of sensor data, a MySQL derivate is not what I'd choose
- sedatk 2y agoWhy is that?
- theshrike79 2y agoRDBMS isn't the best place to store time series data. There are better and more efficient options for that.
- callmemclovin 2y agoI'm a noob when it comes to DBs, but stumbled upon using InfluxDB with Home Assistant - would you say that's a solid choice, or are there better alternatives out there?
- theshrike79 2y agoInfluxDB is pretty much the most popular and widely used time series database. The difference between just storing every value ever and a time series DB is that the latter one can reduce the data frequency when it gets older. Like if you're measuring your fridge temperature, you might store it every minute. But do you care about 1 minute accuracy when the data is two years old? Would 5 or 15 minutes be enough? This is what time series DBs do automatically. They're also optimised for data that's formatted as <time stamp> - <values>, making inserts and queries fast for data like that.
- lannisterstark 2y agoTimeflux or some such are better alternative to store timeseries data.
- rsanek 2y ago15GB is tiny, db selection doesn't really matter at that small of a scale
- theshrike79 2y agoDepends. 15GB on an actual server? Peanuts. 15GB MariaDB/Mysql database on a Raspberry Pi SD card? Recipe for disaster.