Updated FAQ (markdown)

Aliaksandr Valialkin 2018-10-10 19:09:05 +03:00
parent 23d53e1fd6
commit a1a063e147

2
FAQ.md

@ -44,7 +44,7 @@
* Q: _Are there performance comparisons with other solutions?_ * 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. Please note that VictoriaMetrics perfectly scales on multiple instances, so it should achieve xN better results on N instances.