From 41d23f84ed5fe8c6c0857cc6b897466023ab80ae Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Fri, 14 Aug 2020 19:15:25 +0300 Subject: [PATCH] docs/Cluster-VictoriaMetrics.md: sync with upstream --- docs/Cluster-VictoriaMetrics.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index c878ca4f6..bff3e1400 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -259,8 +259,8 @@ Each instance type - `vminsert`, `vmselect` and `vmstorage` - can run on the mos * The recommended total number of vCPU cores for all the `vminsert` instances can be calculated from the ingestion rate: `vCPUs = ingestion_rate / 150K`. * The recommended number of vCPU cores per each `vminsert` instance should equal to the number of `vmstorage` instances in the cluster. * The amount of RAM per each `vminsert` instance should be 1GB or more. RAM is used as a buffer for spikes in ingestion rate. - The maximum amount of used RAM per `vminsert` node can be tuned with `-memory.allowedPercent` command-line flag. For instance, `-memory.allowedPercent=20` - limits the maximum amount of used RAM to 20% of the available RAM on the host system. + The maximum amount of used RAM per `vminsert` node can be tuned with `-memory.allowedPercent` or `-memory.allowedBytes` command-line flags. + For instance, `-memory.allowedPercent=20` limits the maximum amount of used RAM to 20% of the available RAM on the host system. * Sometimes `-rpc.disableCompression` command-line flag on `vminsert` instances could increase ingestion capacity at the cost of higher network bandwidth usage between `vminsert` and `vmstorage`.