Ever-increasing RAM usage with low series cardinality

[bongo]

So far this worked best for me and brought influx to a moderate memory usage of ~3GiB

How to prevent OOM exceptions when importing billions of data points

I’d also suggest taking a look at this FAQ entry regarding backfilling sparse data. For backfilling data, there are a couple is things that need to be adjusted depending on the shape of your data. Range of time - If you are backfilling years of data, you will most likely need to increase the shard duration on your retention policy as the default of 1w will end up creating lots of shards. If you do not plan on deleting the data, the larger the duration the better. Density - If you have spar…

1. Lower cache-snapshot-write-cold-duration to 10s during backfilling
2. create default retention policy with long shard duration e.g. create database sensors with duration INF shard duration 5200w name longterm

This essentially locks the number of shard groups being created to one (expecting a daterange smaller than 100y). influxdb then manages the tsm files within the group itself (so you should not lose performance, It’s designed to work this way).