Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reference blog post in cost section #3827

Merged
merged 2 commits into from
Sep 14, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/operating/aws-costs.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion docs/overview/introduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)