mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2025-03-21 15:45:01 +00:00
25aa4f1d30
* make QuickStart first, similarly to vlogs docs * push release guide to bottom, as it is not for users Signed-off-by: hagen1778 <roman@victoriametrics.com>
92 lines
4.5 KiB
Markdown
92 lines
4.5 KiB
Markdown
---
|
|
weight: 22
|
|
title: Best practices
|
|
menu:
|
|
docs:
|
|
identifier: vm-best-practices
|
|
parent: 'victoriametrics'
|
|
weight: 22
|
|
aliases:
|
|
- /BestPractices.html
|
|
---
|
|
## Install Recommendation
|
|
|
|
It is recommended running the latest available release of VictoriaMetrics from [this page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest),
|
|
since it contains all the bugfixes and enhancements.
|
|
|
|
There is no need to tune VictoriaMetrics because it uses reasonable defaults for command-line flags. These flags are automatically adjusted for the available CPU and RAM resources. There is no need in Operating System tuning because VictoriaMetrics is optimized for default OS settings. The only option is to increase the limit on the [number of open files in the OS](https://medium.com/@muhammadtriwibowo/set-permanently-ulimit-n-open-files-in-ubuntu-4d61064429a), so VictoriaMetrics could accept more incoming connections and could keep open more data files.
|
|
|
|
## Filesystem
|
|
|
|
The recommended filesystem for VictoriaMetrics is [ext4](https://en.wikipedia.org/wiki/Ext4). If you plan to store more than 1TB of data on ext4 partition or plan to extend it to more than 16TB, then the following options are recommended to pass to mkfs.ext4:
|
|
|
|
```sh
|
|
mkfs.ext4 ... -O 64bit,huge_file,extent -T huge
|
|
```
|
|
|
|
VictoriaMetrics should work OK with other filesystems too.
|
|
|
|
## Operating System
|
|
|
|
VictoriaMetrics is production-ready for the following operating systems:
|
|
|
|
* Linux (Alpine, Ubuntu, Debian, RedHat, etc.)
|
|
* FreeBSD
|
|
* OpenBSD
|
|
* Solaris/SmartOS
|
|
|
|
There is an experimental support of VictoriaMetrics components for Windows.
|
|
|
|
VictoriaMetrics can run also on MacOS for testing and development purposes.
|
|
|
|
## Supported Architectures
|
|
|
|
* **Linux**: i386, amd64, arm, arm64, ppc64le
|
|
* **FreeBSD**: i386, amd64, arm
|
|
* **OpenBSD**: i386, amd64, arm
|
|
* **Solaris/SmartOS**: i386, amd64
|
|
* **MacOS**: amd64, arm64 (for testing and development purposes)
|
|
* **Windows**: amd64
|
|
|
|
## Kubernetes
|
|
|
|
VictoriaMetrics natively supports deployment in Kubernetes via [helm charts](https://docs.victoriametrics.com/helm/)
|
|
and [kubernetes operator](https://docs.victoriametrics.com/operator/). See how to [start using k8s operator](https://docs.victoriametrics.com/guides/getting-started-with-vm-operator/).
|
|
|
|
Common recommendations:
|
|
1. Prefer setting [requests equal to limits](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits)
|
|
for stateful components like [vmstorage](https://docs.victoriametrics.com/cluster-victoriametrics/#architecture-overview) to avoid unnecessary
|
|
component restarts.
|
|
|
|
1. Avoid using [fractional CPU units](https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/#cpu-units)
|
|
when setting resources for optimal performance. VictoriaMetrics is written in Go and its runtime requires specifying
|
|
[integer number](https://pkg.go.dev/runtime#GOMAXPROCS) of concurrently running threads.
|
|
When fractional CPU unit is specified, VictoriaMetrics will automatically round it down.
|
|
|
|
## Upgrade procedure
|
|
|
|
It is safe to upgrade VictoriaMetrics to new versions unless the [release notes](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest) say otherwise.
|
|
It is safe to skip multiple versions during the upgrade unless release notes say otherwise. It is recommended to perform regular upgrades to the latest version,
|
|
since it may contain important bug fixes, performance optimizations or new features.
|
|
|
|
It is also safe to downgrade to the previous version unless release notes say otherwise.
|
|
|
|
The following steps must be performed during the upgrade / downgrade procedure:
|
|
|
|
* Send SIGINT signal to VictoriaMetrics process so that it is stopped gracefully.
|
|
* Wait until the process stops. This can take a few seconds.
|
|
* Start the upgraded VictoriaMetrics.
|
|
|
|
## Backup Recommendations
|
|
|
|
VictoriaMetrics supports backups via [vmbackup](https://docs.victoriametrics.com/vmbackup/) and [vmrestore](https://docs.victoriametrics.com/vmrestore/) tools. There is also [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager/), which simplifies backup automation.
|
|
|
|
## Technical Support and Services
|
|
|
|
There are the following channels for providing technical support for VictoriaMetrics:
|
|
|
|
* [GitHub issues](https://github.com/VictoriaMetrics/VictoriaMetrics/issues)
|
|
* [Slack Inviter](https://slack.victoriametrics.com/) and [Slack channel](https://victoriametrics.slack.com/)
|
|
* [Telegram channel](https://t.me/VictoriaMetrics_en)
|
|
|
|
We also provide [Enterprise support](https://docs.victoriametrics.com/enterprise/).
|