Thoughts on Time-series Databases

Re:Thoughts on Time-series Databases by bane on Tuesday June 30, 2015 @04:04PM (#9808071)

> 20 million rows

> 30 seconds

Ugh, that's terrible. grepping the file or reading and parsing a csv file is probably faster.

[ Parent | on HN ]

Re:Thoughts on Time-series Databases by Everlag on Tuesday June 30, 2015 @04:14PM (#9808126)

It was pretty awful watching the vps choke to death when I tried implementing any feature using full set prices. Pegged at 99% cpu usage with the go garbage collector frantically trying to not let the process crash... that was not an environment I wanted to take to production.

[ Parent | on HN ]

Re:Thoughts on Time-series Databases by bane on Wednesday July 01, 2015 @12:24AM (#9810063)

Could it be the environment didn't have enough memory to do things? I've seen frantic swapping and garbage collection before in VMs without enough RAM.

[ Parent | on HN ]

Re:Thoughts on Time-series Databases by martindale on Tuesday June 30, 2015 @07:52PM (#9809132)

> vps

There's your problem. If you're at the "make it fast" part of "make it work, make it right, make it fast", you should almost certainly be on dedicated hardware.

[ Parent | on HN ]

Re:Thoughts on Time-series Databases by Everlag on Tuesday June 30, 2015 @10:42PM (#9809793)

That was actually the "make it work" portion: I was attempting to grab some 10 full set prices at a time for a gallery feature and managed to crash the influxdb.

[ Parent | on HN ]