mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-26 20:30:10 +01:00
9f42fccfc2
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
|
||
---|---|---|
.. | ||
common | ||
csvimport | ||
datadogsketches | ||
datadogv1 | ||
datadogv2 | ||
graphite | ||
influx | ||
native | ||
newrelic | ||
opentelemetry | ||
opentsdb | ||
opentsdbhttp | ||
prometheusimport | ||
prompush | ||
promremotewrite | ||
relabel | ||
static/css | ||
vmimport | ||
main.go | ||
README.md |
vminsert
routes the ingested data to vmstorage
.