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
Announcing Prometheus 3.0
Announcing Prometheus 3.0

The Prometheus Team Nov 14, 2024 30 views

2
Interview with Hostinger
Interview with Hostinger

Brian Brazil Feb 6, 2019 29 views

3
Custom service discovery with etcd
Custom service discovery with etcd

Fabian Reinartz Aug 17, 2015 29 views

5
Interview with JustWatch
Interview with JustWatch

Brian Brazil Oct 12, 2016 28 views