菜单
Guides Qdrant scaling decisions. Use when someone asks 'how many nodes do I need', 'data doesn't fit on one node', 'need more throughput', 'cluster is slow', 'too many tenants', 'vertical or horizontal', 'how to shard', or 'need to add capacity'.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/qdrant/skills --skill qdrant-scaling命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | qdrant-scaling |
| description | Guides Qdrant scaling decisions. Use when someone asks 'how many nodes do I need', 'data doesn't fit on one node', 'need more throughput', 'cluster is slow', 'too many tenants', 'vertical or horizontal', 'how to shard', or 'need to add capacity'. |
| allowed-tools | ["Read","Grep","Glob"] |
| Symptom | Sub-skill |
|---|---|
| Data does not fit on a single node | Scaling Data Volume |
| Running out of disk or memory as the dataset grows | Scaling Data Volume |
| Need to shard the collection across more nodes | Scaling Data Volume |
| Cannot handle enough parallel queries | Scaling for Query Throughput |
| Need higher QPS | Scaling for Query Throughput |
| A single query is too slow | Scaling for Query Latency |
| Need to cut the tail latency of individual requests |
| Queries return very large result sets and slow down | Scaling for Query Volume |
First determine what you're scaling for:
After determining the scaling goal, we can choose scaling strategy based on tradeoffs and assumptions. Each pulls toward different strategies. Scaling for throughput and latency are opposite tuning directions.
This becomes relevant when volume of the dataset exceeds the capacity of a single node. Read more about scaling for data volume in Scaling Data Volume
If your system needs to handle more parallel queries than a single node can handle, then you need to scale for query throughput.
Read more about scaling for query throughput in Scaling for Query Throughput
Latency of a single query is determined by the slowest component in the query execution path. It is in sometimes correlated with throughput, but not always. It might require different strategies for scaling.
Read more about scaling for query latency in Scaling for Query Latency
By query volume we understand the amount of results that a single query returns. If the query volume is too high, it can cause performance issues and increase latency.
Tuning for query volume is opposite might require special strategies.
Read more about scaling for query volume in Scaling for Query Volume
