Qdrant Scaling

作者 qdrant6a03d0ce8f55无许可证收录于 2026年10月8日更新于 2026年10月8日

Guides Qdrant scaling decisions. Use when someone asks 'how many nodes do I need', 'data doesn't fit on one node', 'need more throughput or QPS', 'CPU is pegged / can't keep up with the request rate', 'one query is slow / p99 or tail latency too high', 'cluster is slow', 'too many tenants', 'vertical or horizontal', 'how to shard', 'need to add capacity', 'large limit / pagination / scroll is slow', or 'only recent data matters / expiring old vectors / retention window'.

仅含说明DevOps & Cloud
AI 生成的概览

将 Qdrant 扩缩容问题路由到数据量、QPS、延迟、查询量和分片相关指南。

功能
该技能是 Qdrant 扩缩容指南的路由索引。它把用户描述的症状(例如数据无法放入单个节点、吞吐不足、尾延迟过高、结果集过大、租户过多或需要数据保留)匹配到具体的指南文件,并要求代理读取该文件后据此作答。它还指出延迟与吞吐在分段数量设置上方向相反。
适用场景
当有人询问需要多少 Qdrant 节点、应垂直还是水平扩展、如何分片、如何提高 QPS、如何降低 p99 延迟、如何处理大 limit 或分页,或如何让旧向量过期时使用。
运行要求
需要所引用的指南文件存在且可读取;该技能声明使用 Read、Grep 和 Glob 工具,自身不附带脚本。

Qdrant Scaling

Route first, then answer. Match the user's symptom in the table, Read that file, and answer from it. Do not answer from this page alone: it contains routing only, not the guidance. If two rows match, read both.

The user saysRead
Data does not fit on a single node, running out of disk or memory as the dataset growsscaling-data-volume/SKILL.md
Need to shard the collection across more nodes, data outgrew one nodescaling-data-volume/SKILL.md
Cannot handle enough parallel queries, need higher QPS or throughputscaling-qps/SKILL.md
Can't hold the request rate, CPU is peggedscaling-qps/SKILL.md
A single query is too slow, need to cut the tail latency of individual requestsminimize-latency/SKILL.md
p99 or tail latency too high, but traffic/QPS is fineminimize-latency/SKILL.md
Queries return very large result sets and slow downscaling-query-volume/SKILL.md
Large limit, top-1000 queries, pagination, scroll across shardsscaling-query-volume/SKILL.md
Many tenants or customers, one collection each, tenant isolationscaling-data-volume/tenant-scaling/SKILL.md
Only recent data matters, retention, expiring old vectors, time-based rotationscaling-data-volume/sliding-time-window/SKILL.md
Single node no longer fits the workload, before deciding to shardscaling-data-volume/vertical-scaling/SKILL.md
Already vertically maxed out, need more nodes, reshardingscaling-data-volume/horizontal-scaling/SKILL.md

Latency and throughput pull opposite ways on segment count. For latency, increase segments toward the CPU core count (default_segment_number: 16). For throughput, use fewer and larger segments (default_segment_number: 2). Applying the wrong direction makes the reported problem worse.

来源与署名

来源:qdrant/skills位于skills/qdrant-scaling提交6a03d0c

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架