qdrant-search-speed-optimization
Diagnoses and fixes slow Qdrant search. Use when someone reports 'search is slow', 'high latency', 'queries take too long', 'low QPS', 'throughput too low', 'filtered search is slow', or 'search was fast but now it's slow'. Also use when search performance degrades after config changes or data growth.
Profile →npx skills add github/awesome-copilot --skill search-speed-optimization --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Diagnose a problem There the multiple possible reasons for search performance degradation. The most common ones are: * Memory pressure: if the working set exceeds available RAM * Complex requests (e.g. high `hnsw_ef`, complex filters without payload index) * Competing background processes (e.g. optimizer still running after bulk upload) * Problem with the cluster (e.g. network issues, hardware degradation) ## Single Query Too Slow (Latency) Use when: individual queries take too long regardless of load. ### Diagnostic steps: - Check if second run of the same request is significantly faster (indicates memory pressure) - Try the same query with `with_payload: false` and `with_vectors: false` to see if payload retrieval is the bottleneck - If request uses filters, try to remove them one by one to identify if a specific filter condition is the bottleneck ### Common fixes: - Tune HNSW parameters: [Fine-tuning search](https://search.qdrant.tech/md/documentation/operations/optimize/?s=fine-tuning-search-parameters) - Enable in-memory quantization: [Scalar quantization](https://search.qdrant.tech/md/documentation/manage-data/quantization/?s=scalar-quantization) - Reduce Vector Dimensional
- Single Query Too Slow (Latency)
- Diagnostic steps:
- Common fixes:
- Can't Handle Enough QPS (Throughput)
- Filtered Search Is Slow
- Optimize search performance with parallel updates
- Diagnostic steps
- Recommended configuration changes
- What NOT to Do
What does the qdrant-search-speed-optimization skill do?
Diagnoses and fixes slow Qdrant search. Use when someone reports 'search is slow', 'high latency', 'queries take too long', 'low QPS', 'throughput too low', 'filtered search is slow', or 'search was fast but now it's slow'. Also use when search performance degrades after config changes or data growth.
How do I install it?
Run `npx skills add github/awesome-copilot --skill search-speed-optimization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.