We tried InfluxDB -> it would just crumble under the amount of data single server generates. You would basically need a dedicated influxdb server per shared hosting server. We tried several others as well.
They don't work faster then MySQL/PgSQL for what we need. We spend about 3 months trying to adopt them before we gave up.
Also, same db that takes 2GB in sqlite took about 30GB in influxdb. We tried multiple engines, optimizations, performance recommendations, etc...
We might try again in another 9-12 months - but so far, none of them have low enough footprint for us to be able to use it.
Igor Seletskiy
We tried InfluxDB -> it would just crumble under the amount of data single server generates. You would basically need a dedicated influxdb server per shared hosting server. We tried several others as well.
They don't work faster then MySQL/PgSQL for what we need. We spend about 3 months trying to adopt them before we gave up.
Also, same db that takes 2GB in sqlite took about 30GB in influxdb. We tried multiple engines, optimizations, performance recommendations, etc...
We might try again in another 9-12 months - but so far, none of them have low enough footprint for us to be able to use it.