From a1a063e1478d814563a9e83689ffa819c10a1001 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Wed, 10 Oct 2018 19:09:05 +0300 Subject: [PATCH] Updated FAQ (markdown) --- FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index 8140883..5e529b5 100644 --- a/FAQ.md +++ b/FAQ.md @@ -44,7 +44,7 @@ * Q: _Are there performance comparisons with other solutions?_ - A: We modified [tsbs benchmark from TimescaleDB](https://blog.timescale.com/time-series-database-benchmarks-timescaledb-influxdb-cassandra-mongodb-bc702b72927e) and run single-server performance tests for VictoriaMetrics, TimescaleDB and InfluxDB. Results are available [here](https://docs.google.com/spreadsheets/d/158AAsLMlGZ72D4MHfSdru_9dt3jpHymqo8Up_vp3LfU/edit?usp=sharing). In short, VictoriaMetrics is up to 8x faster than TimescaleDB and InfluxDB on heavy queries. Additionally, it uses 1/70th of storage space for test data comparing TimescaleDB. + A: We modified [tsbs benchmark from TimescaleDB](https://blog.timescale.com/time-series-database-benchmarks-timescaledb-influxdb-cassandra-mongodb-bc702b72927e) and run single-server performance tests for VictoriaMetrics, TimescaleDB and InfluxDB. Results are available [here](https://docs.google.com/spreadsheets/d/158AAsLMlGZ72D4MHfSdru_9dt3jpHymqo8Up_vp3LfU/edit?usp=sharing). In short, VictoriaMetrics is up to 8x faster than TimescaleDB and InfluxDB on heavy queries when run on the same hardware. Additionally, it uses 1/70th of storage space for test data comparing to TimescaleDB. Please note that VictoriaMetrics perfectly scales on multiple instances, so it should achieve xN better results on N instances.