Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →qdrant/qdrant-performance-optimization
Navigation hub linking sub-skills for proactive Qdrant tuning: search speed, indexing performance, and memory usage optimization.
Passed 14 of 21 test cases with the skill, and 5 of 21 without it.
and 6 more in the full report
12 fixed3 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
In Qdrant Web UI, our vector collection status is stuck in yellow state and segment optimization runs continuously without finishing. Which file should be read to diagnose stalled optimization?
| Checked | Without skill | With skill |
|---|---|---|
| The response identifies indexing-performance-optimization/SKILL.md as the file to read. | Missed | Passed |
The instructions your model reads when the skill loads.
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 |
|---|---|
| Filtered queries much slower than unfiltered | search-speed-optimization/SKILL.md |
| Low QPS, cannot handle the query load | search-speed-optimization/SKILL.md |
| Individual queries take too long to return | search-speed-optimization/SKILL.md |
| Index build or HNSW build takes too long, vector upload is slow | indexing-performance-optimization/SKILL.md |
| Collection stays yellow, optimizer stuck or runs for a long time | indexing-performance-optimization/SKILL.md |
| Bulk upsert of vectors is slow | indexing-performance-optimization/SKILL.md |
| RAM usage too high, out-of-memory crashes | memory-usage-optimization/SKILL.md |
| Want to fit a larger dataset on the same hardware | memory-usage-optimization/SKILL.md |
| Reducing cost by moving data to disk | memory-usage-optimization/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.
test cases passed, vs 5 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.