跳到主要內容
AI News HubLIVE
公開文章 18採集文章 29可信度 82刷新頻率 120 分鐘
健康狀態 健康來源類型 官方原文權限 官方原文最近入庫 2026-09-17ID qdrant-blog運行狀態 已啟用

Official vector database and AI infrastructure feed; confirm reuse terms before full body display.

最新公開文章

待翻譯:Hyperbolic Embeddings in Qdrant

AI 服務暫時不可用,以下為來源摘要,待恢復後補全翻譯:We choose embedding models, dimensions, and indexes. The geometry usually comes with the package. But why use a flat space, and what else could we choose? What Is a Manifold, and Where Do Our Vectors Live? A manifold is the space our embeddings live in. For embeddings, we care about the geometry we give that space. It determines how we measure distance, what the shortest path looks like, and how much room there is as we move outward.

Qdrant Blog站內正文待翻譯:Hyperbolic Embeddings in Qdrant

待翻譯:Hybrid Search in Qdrant

AI 服務暫時不可用,以下為來源摘要,待恢復後補全翻譯:A search result can look plausible and still be wrong. Dense retrieval can return a document on the right topic but miss an exact identifier copied into the query. Sparse retrieval can miss a relevant document when the query describes it with terms the corpus doesn’t use. Either way, your logs record a successful query. Hybrid search runs dense and sparse retrieval over the same query, then merges their result lists. Dense retrieval adds semantic similarity, so paraphrases can rank together. Sparse retrieval adds weighted term matching for exact words and identifiers.

Qdrant Blog站內正文待翻譯:Hybrid Search in Qdrant

待翻譯:When Your Collection Outgrows RAM

AI 服務暫時不可用,以下為來源摘要,待恢復後補全翻譯:Once a collection no longer fits in RAM, the kernel evicts vector pages, and the next query waits on a disk read to get them back. Quantization buys that memory back. Qdrant keeps a compressed copy of each dense vector in RAM and moves the full-precision originals to disk. TurboQuant is the method measured here. It rotates each vector before compressing it, which spreads the error evenly across coordinates, and its bits parameter sets the depth from bits4 down to bits1. Start at bits4, a good default for many workloads at eight times compression.

Qdrant Blog站內正文待翻譯:When Your Collection Outgrows RAM

待翻譯:When Is a Reranker Worth It?

AI 服務暫時不可用,以下為來源摘要,待恢復後補全翻譯:Before you tune a reranker, use the pre-tuning checks to verify index state and set a labeled baseline. Your candidate list can already contain documents your ranking never shows. Score those candidates as if they were perfectly ordered, then compare that with the score your pipeline returns today. The gap between the two is everything a better ranking stage could recover, so measure it before you reach for a model. Use nDCG@10, which grades the top 10 results and gives more credit to relevant documents near the top.

Qdrant Blog站內正文待翻譯:When Is a Reranker Worth It?

待翻譯:How to Tune Hybrid Search in Qdrant

AI 服務暫時不可用,以下為來源摘要,待恢復後補全翻譯:Before you tune fusion, use the pre-tuning checks to verify index state and set a labeled baseline. Hybrid search retrieves dense and sparse candidate lists, then fuses them into one ranking. The dense prefetch finds similar meaning; the sparse prefetch finds matching keywords. Fusion reorders the candidates the prefetches return, so a document missing from both lists cannot appear in the result. Confirm Fusion Beats Either Prefetch Before tuning, compare dense retrieval, sparse retrieval, and default Reciprocal Rank Fusion (RRF) at k=2 and equal weights. Score all three with nDCG@10, which grades the top 10 results and gives more credit to relevant documents near the top.

Qdrant Blog站內正文待翻譯:How to Tune Hybrid Search in Qdrant

待翻譯:Candidate Depth: How Much Retrieval Is Enough?

AI 服務暫時不可用,以下為來源摘要,待恢復後補全翻譯:Before you tune candidate depth, use the pre-tuning checks to verify index state and set a labeled baseline. Everything below measures against that baseline. Candidate depth is the number of candidates a retrieval stage passes to a later ranking stage. It matters only when a later stage can use the extra candidates. In hybrid search, every prefetch carries its own limit, and a multi-stage query that nests one prefetch inside another sets a depth at each level. In dense-only or sparse-only search, it is the number of candidates you pass to a reranker or other downstream stage.

Qdrant Blog站內正文待翻譯:Candidate Depth: How Much Retrieval Is Enough?

待翻譯:What to Check Before Tuning a Qdrant Collection

AI 服務暫時不可用,以下為來源摘要,待恢復後補全翻譯:Before you change a setting, decide what better retrieval means for your workload. The right document at rank one, more candidates for a reranker, lower latency, and a smaller memory footprint each favor different settings, so pick your goal first. If your labeled queries can’t detect the improvement you’re chasing, you won’t be able to tell whether a change helped. Some settings are there to verify correctness, not to tune performance. If a vector is unindexed, a sparse vector is missing the IDF modifier, or the BM25 average length is wrong, the results are invalid. Any benchmark or comparison you run after that will reflect a broken setup. This article shows you how to check each setting and what the correct state looks like.

Qdrant Blog站內正文待翻譯:What to Check Before Tuning a Qdrant Collection

待翻譯:Filtered Vector Search: What ACORN Fixes, and What Fixes ACORN

AI 服務暫時不可用,以下為來源摘要,待恢復後補全翻譯:Filtered vector search breaks when metadata filters turn a healthy nearest-neighbor graph into scattered islands. HNSW’s m parameter controls how many links each point gets. At Qdrant’s default m=16, the one-million-point collection benchmarked below averaged about 21 links per node on layer 0. Filter out 96% of the points and fewer than one link per node survives on average, so traversal can get stranded before it reaches the true nearest matches.

Qdrant Blog站內正文待翻譯:Filtered Vector Search: What ACORN Fixes, and What Fixes ACORN

無需大語言模型的弱檢索預測

大多數檢索系統對所有查詢使用單一管道,這種做法既不合適:單一管道對困難查詢服務不足,對簡單查詢則浪費計算資源。本文提出了無需大語言模型的廉價信號——如分數分散和檢索器一致性——來檢測弱檢索,從而實現僅在需要時進行選擇性升級。

Qdrant Blog站內正文無需大語言模型的弱檢索預測

Qdrant中的TurboQuant

Qdrant 1.18推出了TurboQuant,一種基於Google Research的旋轉向量量化方法,並進行了擴展以適用於生產級嵌入。它提供4位、2位、1.5位和1位的量化選項,在壓縮率和召回率上優於或相當於標量量化(SQ)和二進制量化(BQ)。本文介紹了TurboQuant的原理、Qdrant的增強實現(長度歸一化和各座標校準)以及基準測試結果。

Qdrant Blog站內正文Qdrant中的TurboQuant

針對電商搜索微調稀疏嵌入 | 第2部分:在Modal上訓練SPLADE

本文是五部分系列的第二部分,介紹瞭如何在Modal的無服務器GPU上訓練SPLADE模型,使用Amazon ESCI數據集進行電商搜索。文章涵蓋了數據加載、產品文本格式化、Modal應用設置、SPLADE模型創建、訓練函數、SpladeLoss理解、YAML配置、並行超參數搜索以及避免的陷阱。目標是構建一個針對電商搜索優化的稀疏嵌入模型。

Qdrant Blog站內正文針對電商搜索微調稀疏嵌入 | 第2部分:在Modal上訓練SPLADE

微調稀疏嵌入用於電子商務搜索 | 第一部分:為什麼稀疏嵌入優於 BM25

本文是系列文章的第一部分,探討了在電子商務搜索中微調稀疏嵌入的優勢。與密集嵌入相比,稀疏嵌入保留了精確匹配的關鍵細節,避免了語義模糊導致的不相關結果。文章介紹了SPLADE模型的工作原理、查詢擴展能力以及Qdrant數據庫對稀疏向量的原生支持。通過微調,該系統在Amazon ESCI數據集上實現了比BM25高出29%的性能提升。

Qdrant Blog站內正文微調稀疏嵌入用於電子商務搜索 | 第一部分:為什麼稀疏嵌入優於 BM25

基於距離的數據探索

本文介紹如何利用Qdrant的距離矩陣API進行數據探索,包括降維、聚類和圖表示等方法,幫助發現大規模非結構化數據中的隱藏結構。

Qdrant Blog站內正文基於距離的數據探索

Qdrant 2024年夏季代碼計劃——Python中的ONNX交叉編碼器

本文中,Huong (Celine) Hoang分享了她在Qdrant夏季代碼計劃期間將ONNX交叉編碼器集成到FastEmbed庫的經歷。該項目通過相關性分數實現搜索結果重排序,增強了上下文感知搜索應用的能力。主要挑戰包括構建新的輸入輸出方案、分詞處理、模型加載與測試。該功能已在FastEmbed 0.4.0中可用。

Qdrant Blog站內正文Qdrant 2024年夏季代碼計劃——Python中的ONNX交叉編碼器

什麼是向量數據庫?

本文介紹向量數據庫的基本概念、與傳統數據庫的區別、核心組件(ID、維度、負載)、架構(集合、距離度量、存儲)、主要功能(索引、搜索、更新、刪除),以及密集向量與稀疏向量、混合搜索、量化、分佈式部署、多租户和數據安全等高級特性。

Qdrant Blog站內正文什麼是向量數據庫?

什麼是向量量化?

向量量化是一種用於壓縮高維數據的技術,通過減少內存佔用同時保留關鍵信息,實現更高效的存儲和搜索。本文介紹了三種主要的量化方法:標量量化、二進制量化和乘積量化,並討論瞭如何平衡精度、速度和壓縮率。

Qdrant Blog站內正文什麼是向量量化?

Qdrant 1.7.0 正式發佈!

Qdrant 1.7.0 引入了對稀疏向量的原生支持,實現了關鍵詞搜索與語義搜索的混合檢索;全新的 Discovery API 提供了更精確的向量搜索方式,包括髮現搜索和上下文搜索;用户自定義分片功能允許靈活控制數據分佈;基於快照的分片傳輸機制提升了集羣擴展效率。此外,還包含多項性能優化和穩定性改進。

Qdrant Blog站內正文Qdrant 1.7.0 正式發佈!

關於非結構化數據、向量數據庫、AI新時代以及我們的種子輪融資

Qdrant宣佈完成750萬美元種子輪融資,由Unusual Ventures領投。文章討論向量數據庫在AI時代的重要性,非結構化數據的爆炸式增長,以及Qdrant作為開源向量相似性搜索解決方案的進展和未來計劃。

Qdrant Blog站內正文關於非結構化數據、向量數據庫、AI新時代以及我們的種子輪融資

全部來源