On 02.03.24 08:00, Mirco wrote: > Any reason samples are still encoded as a list of pairs? Using two arrays > would both reduce the number of objects and allow using varint encoding for > timestamps.
I assume you are referring to the protobuf messages for TimeSeries and Sample? I'm not an expert for remote write (and even less so for remote read), but I think it's safe to say that a change in the protobuf layout would mean a new major version of the protocols. v2 is just underway, so that would require the next major version bump to v3, which would be a big deal given how widely used the protocol is. Having said that, at least for remote write, there are usually not a lot of samples in a TimeSeries message. The most common number is AFAIK one. Mileage might vary for remote read, but that's also far less used. WRT varint: In my understanding of protobuf, varint will always be used for an int64, even if it is a field in another message. -- Björn Rabenstein [PGP-ID] 0x851C3DA17D748D03 [email] bjo...@rabenste.in -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-developers/ZehS9eE4sHeMC9Hc%40mail.rabenste.in.
