VictoriaMetrics/dashboards
Aliaksandr Valialkin b275983403
lib/writeconcurrencylimiter: improve the logic behind -maxConcurrentInserts limit
Previously the -maxConcurrentInserts was limiting the number of established client connections,
which write data to VictoriaMetrics. Some of these connections could be idle.
Such connections do not consume big amounts of CPU and RAM, so there is a little sense in limiting
the number of such connections. So now the -maxConcurrentInserts command-line option
limits the number of concurrently executed insert requests, not including idle connections.

It is recommended removing -maxConcurrentInserts command-line option, since the default value
for this option should work good for most cases.
2023-01-06 22:07:16 -08:00
..
backupmanager.json dashboards: fix operator datasource variable (#3604) 2023-01-05 16:49:19 -08:00
clusterbytenant.json dashboards: fix operator datasource variable (#3604) 2023-01-05 16:49:19 -08:00
operator.json dashboards: fix operator datasource variable (#3604) 2023-01-05 16:49:19 -08:00
victoriametrics-cluster.json lib/writeconcurrencylimiter: improve the logic behind -maxConcurrentInserts limit 2023-01-06 22:07:16 -08:00
victoriametrics.json lib/writeconcurrencylimiter: improve the logic behind -maxConcurrentInserts limit 2023-01-06 22:07:16 -08:00
vmagent.json dashboards: update vmagent dash (#3411) 2022-11-29 20:29:34 -08:00
vmalert.json dashboards: fix operator datasource variable (#3604) 2023-01-05 16:49:19 -08:00