qdrant-scaling — GitHub Copilot skill: what it does, how to install
Guides Qdrant scaling decisions across data volume, query throughput, latency, and result payload sizes.
npx skills add github/awesome-copilot --skill qdrant-scalingWhat qdrant-scaling does
The skill organizes Qdrant architectural decisions into four distinct goals: dataset volume, throughput, query latency, and query result volume. It maps out trade-offs. Tuning for throughput and tuning for latency pull in opposite directions.
To navigate the scaling guides, it calls the Read, Grep, and Glob tools. It helps evaluate when data exceeds single-node capacity and whether to scale vertically or add shards.
Add this skill if your vector database outgrew a single machine or search latency started climbing. Teams running small test collections on a single instance can skip it.
What it helps with
- Shard Qdrant collections when data exceeds single-node memory
- Increase query throughput under heavy concurrent traffic
- Isolate bottlenecks causing high vector search latency
- Tune cluster performance when queries retrieve large result sets
Example prompts for the agent
- Our data does not fit on one Qdrant node, how should we shard?
- Should I scale Qdrant vertically or horizontally for higher QPS?
- Search latency is climbing under load, how do we tune the cluster?
How to install qdrant-scaling
1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill qdrant-scaling2GitHub CLI
gh skill install github/awesome-copilot qdrant-scaling3Manually: put the files in place
.github/skills/qdrant-scaling/SKILL.md1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill qdrant-scaling -a claude-code2Manually: put the files in place
~/.claude/skills/qdrant-scaling/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/qdrant-scaling/
Manually: put the files in place
.agents/skills/qdrant-scaling/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/qdrant-scaling/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
Platform CLI
gemini skills install https://github.com/github/awesome-copilot --path skills/qdrant-scalingManually: put the files in place
.devin/skills/qdrant-scaling/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set554
The whole set →Similar
Questions about qdrant-scaling
How to install qdrant-scaling in GitHub Copilot?
Run gh skill install github/awesome-copilot qdrant-scaling or npx skills add github/awesome-copilot --skill qdrant-scaling. You can also place it in .github/skills/qdrant-scaling/SKILL.md.
What does qdrant-scaling do?
It advises on cluster architecture, sharding, and node counts based on your primary bottleneck.
Which tools does qdrant-scaling require?
The skill uses Read, Grep, and Glob to reference internal scaling documents.
Source text
SKILL.md · MIT
--- 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 --- # Qdrant Scaling First determine what you're scaling for: - data volume - query throughput (QPS) - query latency - query volume 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. ## Scaling Data Volume 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](scaling-data-volume/SKILL.md) ## Scaling for Query Throughput 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](scaling-qps/SKILL.md) ## Scaling for Query Latency 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](minimize-latency/SKILL.md) ## Scaling for Query Volume 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](scaling-query-volume/SKILL.md)
© github · MIT · github/awesome-copilot