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
Interview with Hostinger
Interview with Hostinger

Brian Brazil Feb 6, 2019 26 views

2
Practical Anomaly Detection
Practical Anomaly Detection

Brian Brazil Jun 18, 2015 26 views

3
Announcing Prometheus 3.0
Announcing Prometheus 3.0

The Prometheus Team Nov 14, 2024 25 views

4
Prometheus to Join the Cloud Native Computing Foundation
Prometheus to Join the Cloud Native Computing Foundation

Julius Volz on behalf of the Prometheus core developers May 9, 2016 25 views

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

@bwplotka Feb 14, 2026 24 views