Nikolay f255800da3 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>		2024-08-13 10:49:09 -04:00
..
consistent_hash_test.go
consistent_hash_timing_test.go	app: consistently use atomic.* types instead of atomic.* functions	2024-02-24 03:06:14 +02:00
consistent_hash.go	app/vminsert/netstorage: prevent from infinite loop when the re-routing is enabled and all the vmstorage nodes are unavailable	2024-02-25 03:24:51 +02:00
insert_ctx_pool.go	app/vminsert: returns back memory optimisation (#6794)	2024-08-13 10:49:09 -04:00
insert_ctx.go	lib/prompb: change type of Label.Name and Label.Value from []byte to string	2024-01-16 20:41:37 +02:00
netstorage_test.go
netstorage.go	app/{vminsert,vmselect}: pass proper args to metrics.UnregisterSet() after a8356f3a26	2024-07-15 20:27:40 +02:00
sort_labels.go