From 5543c040619ef0e17ee3d1df3d3e542dcf3c9584 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Tue, 23 Jan 2024 23:21:04 +0200 Subject: [PATCH] docs/Cluster-VictoriaMetrics.md: document that `vmstorage` doesnt compress data it sends to `vmselect` by default This is a follow-up for cd4f641d323cf0977c2e22915eb75edb765ad090 --- docs/Cluster-VictoriaMetrics.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index fc5d16a29..fe5da5d38 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -596,6 +596,7 @@ Some capacity planning tips for VictoriaMetrics cluster: - Query latency can be reduced by increasing CPU resources per each `vmselect` node, since each incoming query is processed by a single `vmselect` node. Performance for heavy queries scales with the number of available CPU cores at `vmselect` node, since `vmselect` processes time series referred by the query on all the available CPU cores. - If the cluster needs to process incoming queries at a high rate, then its capacity can be increased by adding more `vmselect` nodes, so incoming queries could be spread among bigger number of `vmselect` nodes. - By default `vminsert` compresses the data it sends to `vmstorage` in order to reduce network bandwidth usage. The compression takes additional CPU resources at `vminsert`. If `vminsert` nodes have limited CPU, then the compression can be disabled by passing `-rpc.disableCompression` command-line flag at `vminsert` nodes. +- By default `vmstorage` doesn't compress the data it sends to `vmselect` in order to reduce CPU usage at the cost of additional network bandwidth usage. Pass `-rpc.disableCompression=false` command-line flag at `vmstorage` in order to reduce network bandwidh usage needed for processing queries at the cost of increased CPU usage. See also [resource usage limits docs](#resource-usage-limits).