krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-04 10:28:29 +02:00
Code Issues Packages Projects Releases Wiki Activity

Replaced vector db to serch in content (#2189)

Browse Source 
* replaced "vector database" with "vector search" across the website content

# Conflicts:
#	qdrant-landing/content/headless/main/core-features.md
#	qdrant-landing/content/use-cases/_index.md

* upd wording
This commit is contained in:
trean
2026-03-12 00:40:36 +01:00
committed by GitHub
parent 305aea6b9a
commit 1d8f16f979
27 changed files with 44 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/benchmarks/benchmarks-intro.md
+1 -1
View File
@@ -5,7 +5,7 @@ title: How vector search should be benchmarked?
weight: 1
---
# Benchmarking Vector Databases
# Benchmarking Vector Search
At Qdrant, performance is the top-most priority. We always make sure that we use system resources efficiently so you get the **fastest and most accurate results at the cheapest cloud costs**. So all of our decisions from [choosing Rust](/articles/why-rust/), [io optimisations](/articles/io_uring/), [serverless support](/articles/serverless/), [binary quantization](/articles/binary-quantization/), to our [fastembed library](/articles/fastembed/) are all based on our principle. In this article, we will compare how Qdrant performs against the other vector search engines.