qdrant-scaling
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', 'vertica
- 0
- Installs
- —
- Rating
- —
- Success rate
- 9
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 595d4a47ba673d97… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
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 says | Read |
|---|---|
| Data does not fit on a single node, running out of disk or memory as the dataset grows | scaling-data-volume/SKILL.md |
| Need to shard the collection across more nodes, data outgrew one node | scaling-data-volume/SKILL.md |
| Cannot handle enough parallel queries, need higher QPS or throughput | scaling-qps/SKILL.md |
| Can't hold the request rate, CPU is pegged | scaling-qps/SKILL.md |
| A single query is too slow, need to cut the tail latency of individual requests | minimize-latency/SKILL.md |
| p99 or tail latency too high, but traffic/QPS is fine | minimize-latency/SKILL.md |
| Queries return very large result sets and slow down | scaling-query-volume/SKILL.md |
Large limit, top-1000 queries, pagination, scroll across shards | scaling-query-volume/SKILL.md |
| Many tenants or customers, one collection each, tenant isolation | scaling-data-volume/tenant-scaling/SKILL.md |
| Only recent data matters, retention, expiring old vectors, time-based rotation | scaling-data-volume/sliding-time-window/SKILL.md |
| Single node no longer fits the workload, before deciding to shard | scaling-data-volume/vertical-scaling/SKILL.md |
| Already vertically maxed out, need more nodes, resharding | scaling-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.
Files
9- SKILL.md
0aa31504fc2.3 KB - minimize-latency/SKILL.md
0f38e5469f2.8 KB - scaling-data-volume/SKILL.md
4abc9a15091.9 KB - scaling-data-volume/horizontal-scaling/SKILL.md
de892add703.3 KB - scaling-data-volume/sliding-time-window/SKILL.md
5c25bbb6894.6 KB - scaling-data-volume/tenant-scaling/SKILL.md
30fe6038363.6 KB - scaling-data-volume/vertical-scaling/SKILL.md
e9135f65524.8 KB - scaling-qps/SKILL.md
00b8b427b23.6 KB - scaling-query-volume/SKILL.md
992e499c881.4 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from qdrant/skills8
Qdrant provides client SDKs for various programming languages, allowing easy integration with Qdrant deployments.
Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new proje
Guides building on Qdrant Edge, the embedded in-process shard. Use when someone asks 'how to sync Edge with the server', 'keep a local shard in sync with Qdrant Cloud', 'BM25 or keyword search on Edge', 'hybrid search on Edge', 'embeddings on device', 'Edge snapshots', 'apply a partial snapshot', 'w
Diagnoses and guides Qdrant horizontal scaling decisions. Use when someone asks 'vertical or horizontal?', 'how many nodes?', 'how many shards?', 'how to add nodes', 'resharding', 'data doesn't fit', or 'need more capacity'. Also use when data growth outpaces current deployment.
Setting up and running Qdrant Hybrid Cloud on your own Kubernetes cluster (managed, on-prem, or edge): prerequisites, storage/CSI and backups, installing the Qdrant Cloud agent and operator, creating/exposing/securing clusters, registry mirroring, and secret rotation. Use when someone wants to set u
Explains hybrid search in Qdrant. Use when someone asks 'how do I setup hybrid search?', 'how to combine keyword and semantic search?', 'sparse plus dense vectors?', 'missing keyword matches', 'how to combine results from multiple searches?' and 'combining multiple representations'. Also use for how
Fusing scores from multiple searches into a single ranked result (RRF, DBSF, custom fusion). Use when someone asks 'RRF or DBSF?', 'how to combine sparse and dense', 'how to combine scores from multiple searches?', 'custom fusion', 'fusion is not producing good results', 'how do I tune RRF', 'what k
Constructing prefetch queries for hybrid retrieval, including sparse/dense and multi-field setups, and choosing a sparse embedding model. Use when someone asks 'dense and sparse in one search?', 'how to combine multiple fields for retrieval?', 'payloads or sparse vectors for lexical?', 'which sparse
Related backend skillsscan passed
FastAPI best practices covering project structure, Pydantic v2 schemas, dependency injection, async handlers, authentication, authorization, transactional service layers, and testing with httpx and pytest. Use when building or reviewing FastAPI apps — Pydantic schemas, dependencies, async handlers,
Report browser/API/CLI/job/worker/webhook bugs. (gstack)
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides
Guide for upgrading Stripe API versions, webhook endpoints, server-side SDKs, Stripe.js, and mobile SDKs
PostHog integration for server-side Node.js applications using posthog-node
Create and compose tRPC middleware with t.procedure.use(), extend context via opts.next({ ctx }), build reusable middleware with .concat() and .unstable_pipe(), define base procedures like publicProcedure and authedProcedure. Access raw input with getRawInput(). Logging, timing, OTEL tracing pattern