From 0452cb21ee4679d678d8d207b44d2f890d148d2a Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Sun, 5 Apr 2020 13:47:31 +0300 Subject: [PATCH] docs/FAQ.md: add more articles about VictoriaMetrics performance --- docs/FAQ.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/FAQ.md b/docs/FAQ.md index e2d72b1df1..743c3157e8 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -129,6 +129,8 @@ The architecture is [optimized for storing and querying large amounts of time se Yes: +* [Benchmarking time series workloads on Apache Kudu using TSBS](https://blog.cloudera.com/benchmarking-time-series-workloads-on-apache-kudu-using-tsbs/) +* [Billy: how VictoriaMetrics deals with more than 500 billion rows](https://medium.com/@valyala/billy-how-victoriametrics-deals-with-more-than-500-billion-rows-e82ff8f725da) * [Measuring vertical scalability for time series databases: VictoriaMetrics vs InfluxDB vs TimescaleDB](https://medium.com/@valyala/measuring-vertical-scalability-for-time-series-databases-in-google-cloud-92550d78d8ae). * [Measuring insert performance on high-cardinality time series: VictoriaMetrics vs InfluxDB](https://medium.com/@valyala/insert-benchmarks-with-inch-influxdb-vs-victoriametrics-e31a41ae2893) * [TSBS benchmark on high-cardinality time series: VictoriaMetrics vs InfluxDB vs TimescaleDB](https://medium.com/@valyala/high-cardinality-tsdb-benchmarks-victoriametrics-vs-timescaledb-vs-influxdb-13e6ee64dd6b)