Partitioning best practices

Limited availability

InfluxDB Clustered is currently only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Use the following best practices when defining custom partitioning strategies for your data stored in InfluxDB Clustered.

Partition by tags that you commonly query for a specific value

Custom partitioning primarily benefits queries that look for a specific tag value in the WHERE clause. For example, if you often query data related to a specific ID, partitioning by the tag that stores the ID helps the InfluxDB query engine to more quickly identify what partitions contain the relevant data.

Use tag buckets for high-cardinality tags

Partitioning using distinct values of tags with many (10K+) unique values can actually hurt query performance as partitions are created for each unique tag value. Instead, use tag buckets to partition by high-cardinality tags. This method of partitioning groups tag values into “buckets” and partitions by bucket.

Only partition by tags that always have a value

You should only partition by tags that always have a value. If points don’t have a value for the tag, InfluxDB can’t store them in the correct partitions and, at query time, must read all the partitions.

Avoid over-partitioning

As you plan your partitioning strategy, keep in mind that data can be “over-partitioned”–meaning partitions are so granular that queries end up having to retrieve and read many partitions from the object store, which hurts query performance.

  • Avoid using partition time intervals that are less than one day.

    The partition time interval should be balanced with the actual amount of data written during each interval. If a single interval doesn’t contain a lot of data, it is better to partition by larger time intervals.

  • Don’t partition by tags that you typically don’t use in your query workload.

  • Don’t partition by distinct values of high-cardinality tags. Instead, use tag buckets to partition by these tags.

Was this page helpful?

Thank you for your feedback!

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: