From 99ec7ef28f9fbf16f20c815e06a2f2300e90c718 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Fri, 14 Jul 2023 10:34:29 -0700 Subject: [PATCH] docs/VictoriaLogs: use exact number when comparing efficiency of VictoriaLogs and Elasticsearch --- docs/VictoriaLogs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/VictoriaLogs/README.md b/docs/VictoriaLogs/README.md index a71cf68fa1..e0a0f56575 100644 --- a/docs/VictoriaLogs/README.md +++ b/docs/VictoriaLogs/README.md @@ -15,7 +15,7 @@ VictoriaLogs provides the following key features: See [these docs](https://docs.victoriametrics.com/VictoriaLogs/querying/#command-line) for details. - VictoriaLogs capacity and performance scales linearly with the available resources (CPU, RAM, disk IO, disk space). It runs smoothly on both Raspberry PI and a server with hundreds of CPU cores and terabytes of RAM. -- VictoriaLogs can handle much bigger data volumes than Elasticsearch and Grafana Loki when running on comparable hardware. +- VictoriaLogs can handle up to 30x bigger data volumes than Elasticsearch and Grafana Loki when running on the same hardware. See [these docs](#benchmarks). - VictoriaLogs supports fast full-text search over high-cardinality [log fields](https://docs.victoriametrics.com/VictoriaLogs/keyConcepts.html#data-model) such as `trace_id`, `user_id` and `ip`.