Thoughts on Time-series Databases

Post by sciurus » Thu, Jul 02, 2015, 11:56 PM UTC

Mahn wrote: post #36

Everlag wrote: post #12

I actually just migrated 20 million rows of Magic: the Gathering price data from influxDB to postgres this week. For a few days of effort, I decreased my query latency by an order of a magnitude; a full set query, roughly 270 cards, went from 30 to 3 seconds with a cold cache. The migration was prompted by influxDB 0.8 eating 50% of the VPS' cpu and 77% of the ram while idling. It had no capability to index along any…

Just for the record, InfluxDB 0.9 seems to actually be production ready now. Though it doesn't look there's an easy way to migrate to it yet from 0.8.

Based on the changes in 0.9.1, there's no way that 0.9 was production ready and I'd be very cautious about using it.

https://influxdb.com/blog/2015/07/02/InfluxDB-0_9_1-and-Tele...

Post by Kirth » Mon, Jul 06, 2015, 12:51 PM UTC

Mahn wrote: post #115

Kirth wrote: post #102

Earlier quoted context omitted.

"Seems to be", sure. Sinks like a tanker when you try to actually use it, though. None of the software libraries have been updated for 0.9 yet.

> Sinks like a tanker when you try to actually use it Can you name some examples of this besides the CPU authentication bug? Honest question, I'm considering adding InfluxDB to our stack so I'm genuinely curious.

We've had issues with Influx being a massive resource hog. Not properly persisting data to disk. They openly admit that Influx isn't built to gracefully recover from crashes, and that you will lose data.

This by itself wouldn't be a problem for us. But when you're inserting data points, the entire damn thing seems to become unresponsive. Admin UI freezing, http endpoint no longer responding to queries, ...

I know this product is relatively young and your mileage may vary. They have a long way to go.

Re: Thoughts on Time-series Databases

Re: Thoughts on Time-series Databases