> influxDB 0.8 eating 50% of the VPS' cpu and 77% of the ram while idling
> to [InfluxDB's] credit it barely moved beyond idle resource usage when I was stuffing it full of data.
solution: always be cramming it full of data ?
I don't see how it could idle when you're bulk writing, but when it's not serving any traffic it's taking up 50% of cpu (unless it's doing some kind of indexing or cleanup or something in the background, but you would expect that to eventually quiesce).
> to [InfluxDB's] credit it barely moved beyond idle resource usage when I was stuffing it full of data.
solution: always be cramming it full of data ?
I don't see how it could idle when you're bulk writing, but when it's not serving any traffic it's taking up 50% of cpu (unless it's doing some kind of indexing or cleanup or something in the background, but you would expect that to eventually quiesce).