Andrii Chubatiuk 9cfdbc582f refactoring: changed prompb to prompbmarshal everythere where internal series transformations are happening (#7409) ... ### Describe Your Changes doing similar changes for both vmagent and vminsert (like one in https://github.com/VictoriaMetrics/VictoriaMetrics/pull/7399) ends up with almost same implementations for each of packages instead of having this shared code in one place. one of the reasons is the same Timeseries and Labels structure from different prompb and prompbmarshal packages. My proposal is to use structures from prompb package only to marshal/unmarshal sent/received data, but for internal transformations use only structures from prompbmarshal package Another example, where it already can help to simplify code is streaming aggregation pipeline for vmsingle (now it first marshals prompb.Timeseries to storage.MetricRow and then if streaming aggregation or deduplication is enabled it unmarshals all the series back but to prompbmarshal.Timeseries) ### Checklist The following checks are **mandatory**: - [ ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/).		2024-11-26 12:45:17 +01:00
..
insert_ctx.go	refactoring: changed prompb to prompbmarshal everythere where internal series transformations are happening (#7409)	2024-11-26 12:45:17 +01:00
insert_ctx_pool.go	app/vminsert: returns back memory optimisation (#6794)	2024-08-13 10:56:33 -04:00
sort_labels.go	refactoring: changed prompb to prompbmarshal everythere where internal series transformations are happening (#7409)	2024-11-26 12:45:17 +01:00
streamaggr.go	app/vmagent/remotewrite: follow-up for f153f54d11	2024-07-15 20:24:01 +02:00