github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2025-01-10 15:14:09 +00:00
Code Issues Projects Releases Packages Wiki Activity

docs/FAQ.md: mention that single-node vm is easier to setup and operate than the cluster version of vm

Browse source
This commit is contained in:
Aliaksandr Valialkin 2022-08-31 05:02:15 +03:00
parent 6b0050a028
commit b26de84b4a
No known key found for this signature in database
GPG key ID: A72BEC6CD3D0DED1
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/FAQ.md
View file

@ -317,6 +317,8 @@ between [cluster components](https://docs.victoriametrics.com/Cluster-VictoriaMe
The performance of a single-node VictoriaMetrics scales almost perfectly with the available CPU, RAM and disk IO resources on the host where it runs -
see [this article](https://valyala.medium.com/measuring-vertical-scalability-for-time-series-databases-in-google-cloud-92550d78d8ae).
Single-node VictoriaMetrics is easier to setup and operate comparing to cluster version of VictoriaMetrics.
Given the facts above **it is recommended to use single-node VictoriaMetrics in the majority of cases**.
Cluster version of VictoriaMetrics may be preferred over single-node VictoriaMetrics in the following relatively rare cases: