If you can predict next value in the sequence you can achieve better compression (xor predicted value and actual, not previous and next - <a href="http:&#x2F;&#x2F;users.ices.utexas.edu&#x2F;~burtscher&#x2F;papers&#x2F;dcc06.pdf" rel="nofollow">http:&#x2F;&#x2F;users.ices.utexas.edu&#x2F;~burtscher&#x2F;papers&#x2F;dcc06.pdf</a>), but I don&#x27;t think that Prometheus developers are using this.<p>And BTW, I don&#x27;t believe in 2.5-3.5 bytes per data-point somewhere outside synthetic benchmarks.