When (not) to use varbit chunks
Prometheus Blog

When (not) to use varbit chunks


Summary

Prometheus recently added a new chunk encoding called “varbit” which significantly improves compression (up to 3x better) allowing for more data storage and potentially faster ingestion speeds. However, varbit encoding requires sequential access to data within a chunk, while the previous encoding allowed random access, potentially slowing down queries that request specific, non-adjacent samples. The article recommends sticking with the default double-delta encoding unless you’re facing disk space or I/O limitations, in which case experimenting with varbit encoding could be beneficial.
Read the Original Article

This article originally appeared on Prometheus Blog.

Read Full Article on Original Site

Popular from Prometheus Blog

1
Modernizing Prometheus: Native Storage for Composite Types
Modernizing Prometheus: Native Storage for Composite Types

@bwplotka Feb 14, 2026 12 views

2
Uncached I/O in Prometheus
Uncached I/O in Prometheus

@machine424 Mar 5, 2026 11 views

3
Introducing the Experimental info() Function
Introducing the Experimental info() Function

Arve Knudsen Dec 16, 2025 11 views

4
Announcing Prometheus 3.0
Announcing Prometheus 3.0

The Prometheus Team Nov 14, 2024 11 views

5
Our commitment to OpenTelemetry
Our commitment to OpenTelemetry

@Gouthamve Mar 13, 2024 11 views