From a31e0300919834562dfbf7e25ff8b26b95b4ae7b Mon Sep 17 00:00:00 2001 From: David Myriel Date: Wed, 30 Apr 2025 17:47:55 +0200 Subject: [PATCH] add fixes --- qdrant-landing/content/articles/vector-search-production.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/qdrant-landing/content/articles/vector-search-production.md b/qdrant-landing/content/articles/vector-search-production.md index 92ca971de..1121446cb 100644 --- a/qdrant-landing/content/articles/vector-search-production.md +++ b/qdrant-landing/content/articles/vector-search-production.md @@ -149,7 +149,7 @@ Once all records are inserted, you can rebuild the index in a single pass. Consi > By default, Qdrant uses up to 16 threads for indexing, but if you notice your CPU isn't being fully utilized during indexing, you can increase this number. -✅ **Optimize batch size and concurrency:** Keep your batch size at the default (around 100) and instead increase the number of concurrent processes. Running 50-60 concurrent processes can significantly improve upload performance. Using just one or two processes won't allow you to see the true performance potential. +✅ **Use Batch Processes:** Increase the number of concurrent processes. Running 50-60 processes can significantly improve upload performance. Using just one or two processes won't allow you to see the true performance potential. **Be patient with indexing:** After uploading large datasets, there's a waiting period for indexing to complete. This is normal and can take time depending on your dataset size. @@ -509,8 +509,6 @@ For users of Qdrant's managed cloud service, there's an option to configure RBAC ❌ Don't keep outdated Qdrant versions running—**update regularly**. -❌ Resharding isn't the ultimate solution—**strike a balance between replica and shard counts.** - ## Conclusion In conclusion, **vector search in production** isn't tied to a specific cloud provider or infrastructure. The same core principles of **careful configuration, robust ingestion/indexing, intelligent scaling, thorough backups, strong observability, and security** apply universally. By embracing these fundamentals, you'll deliver fast, reliable, and scalable search for your users, regardless of where your hardware or services run.