From b3efea9a5d71c893122e887d901ec87bf976f6b0 Mon Sep 17 00:00:00 2001 From: Pascal Seitz Date: Wed, 13 Sep 2023 17:15:15 +0800 Subject: [PATCH] reference blog post in cost section --- docs/operating/aws-costs.md | 4 ++++ docs/overview/introduction.md | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/operating/aws-costs.md b/docs/operating/aws-costs.md index 95ca09e554f..37085eabbaa 100644 --- a/docs/operating/aws-costs.md +++ b/docs/operating/aws-costs.md @@ -5,6 +5,10 @@ sidebar_position: 3 Quickwit has been tested on Amazon S3. This page sums up what we have learned from that experience. +## Real World Example +In this [blog post](https://quickwit.io/blog/benchmarking-quickwit-engine-on-an-adversarial-dataset#indexing-costs), we indexed 23 TB of data and evaluated performance and costs. +You may be able to deduce the costs of indexing and querying on your dataset. + ## Data transfers costs and latency Cloud providers charge for data transfers in and out of their networks. In addition, querying an index from a remote machine adds some extra latency. diff --git a/docs/overview/introduction.md b/docs/overview/introduction.md index d63290c6a85..8071908eaed 100644 --- a/docs/overview/introduction.md +++ b/docs/overview/introduction.md @@ -63,4 +63,4 @@ Use cases where you would likely *not* want to use Quickwit include: - [Quickstart](../get-started/quickstart.md) - [Concepts](architecture.md) -- [Last release blog post](https://quickwit.io/blog/quickwit-0.5) +- [Last release blog post](https://quickwit.io/blog/quickwit-0.6)