README.md: mention about multi-tenancy

This commit is contained in:
Aliaksandr Valialkin 2019-06-12 21:30:36 +03:00
parent a8db528930
commit 611c4401f8

View file

@ -75,6 +75,7 @@ Cluster version is available [here](https://github.com/VictoriaMetrics/VictoriaM
- [High availability](#high-availability) - [High availability](#high-availability)
- [Multiple retentions](#multiple-retentions) - [Multiple retentions](#multiple-retentions)
- [Downsampling](#downsampling) - [Downsampling](#downsampling)
- [Multi-tenancy](#multi-tenancy)
- [Scalability and cluster version](#scalability-and-cluster-version) - [Scalability and cluster version](#scalability-and-cluster-version)
- [Security](#security) - [Security](#security)
- [Tuning](#tuning) - [Tuning](#tuning)
@ -444,6 +445,11 @@ These properties reduce the need in downsampling. We plan implementing downsampl
See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/36) for details. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/36) for details.
### Multi-tenancy
Single-node VictoriaMetrics doesn't support multi-tenancy. Use [cluster version](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/cluster) instead.
### Scalability and cluster version ### Scalability and cluster version
Though single-node VictoriaMetrics cannot scale to multiple nodes, it is optimized for resource usage - storage size / bandwidth / IOPS, RAM, CPU. Though single-node VictoriaMetrics cannot scale to multiple nodes, it is optimized for resource usage - storage size / bandwidth / IOPS, RAM, CPU.