跳到主要内容
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新时代以及我们的种子轮融资

全部来源