mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-23 20:37:12 +01:00
eefae85450
### Describe Your Changes Currently, vmagent always uses a separate `http.Client` for every group watcher in Kubernetes SD. With a high number of group watchers this leads to large amount of opened connections. This PR adds 2 changes to address this: - re-use of existing `http.Client` - in case `http.Client` is connecting to the same API server and uses the same parameters it will be re-used between group watchers - HTTP2 support - this allows to reuse connections more efficiently due to ability of using streaming via existing connections. See this issue for the details and test results - https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5971 ### Checklist The following checks are **mandatory**: - [ ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). --------- Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Co-authored-by: Roman Khavronenko <roman@victoriametrics.com> |
||
---|---|---|
.. | ||
discovery | ||
discoveryutils | ||
testdata | ||
client_test.go | ||
client.go | ||
config_test.go | ||
config_timing_test.go | ||
config.go | ||
relabel_debug.go | ||
scraper.go | ||
scrapework_test.go | ||
scrapework_timing_test.go | ||
scrapework.go | ||
targetstatus.go | ||
targetstatus.qtpl | ||
targetstatus.qtpl.go |