Nikolay 9f42fccfc2 app/vminsert: returns back memory optimisation (#6794) ... Production workload shows that it's useful optimisation. Channel based objects pool allows to handle irregural data ingestion requests and make memory allocations more smooth. It's improves sync.Pool efficiency, since objects from sync.Pool removed after 2 GC cycles. With GOGC=30 value, GC runs significantly more often. https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6733 ### Checklist The following checks are **mandatory**: - [ ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: f41gh7 <nik@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit f255800da3) Signed-off-by: hagen1778 <roman@victoriametrics.com> # Conflicts: # app/vminsert/common/insert_ctx_pool.go		2024-08-13 10:56:33 -04:00
..
insert_ctx_pool.go	app/vminsert: returns back memory optimisation (#6794)	2024-08-13 10:56:33 -04:00
insert_ctx.go	lib/streamaggr: skip empty aggregators (#6307)	2024-05-20 14:03:28 +02:00
sort_labels.go	app/{vminsert,vmagent}: add -sortLabels command-line option for sorting time series labels before ingesting them in the storage	2021-03-31 23:27:58 +03:00
streamaggr.go	app/vmagent/remotewrite: follow-up for f153f54d11	2024-07-15 20:24:01 +02:00