Install any skill in seconds. Free to start, no credit card required.
Get Started Free →qdrant/qdrant-scaling-query-volume
Guides Qdrant query volume scaling.
Passed 17 of 22 test cases with the skill, and 8 of 22 without it.
and 16 more in the full report
11 fixed8 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What internal configuration constant or threshold value in Qdrant defines the minimum combined limit and offset required for shard query subsampling?
| Checked | Without skill | With skill |
|---|---|---|
| identifies the threshold constant name as SHARD_QUERY_SUBSAMPLING_LIMIT | Missed | Passed |
| identifies the numeric threshold value as 128 | Missed | Passed |
The instructions your model reads when the skill loads.
Problem: When a query has a large limit (e.g. 1000) and there are multiple shards (e.g. 10), naively each shard must return the full 1000 results — totaling 10,000 scored points transferred and merged. This is wasteful since data is randomly distributed across auto-shards.
Instead of asking every shard for the full limit, ask each shard for a smaller limit computed via Poisson distribution statistics, then merge. This is safe because auto-sharding guarantees random, independent data distribution.
The strategy trades a small probability of slightly incomplete results for a large reduction in inter-shard data transfer, especially for high-limit queries across many shards. The 1.2x safety factor and the 99.9% Poisson threshold keep the error rate very low — comparable to inaccuracies already introduced by approximate vector indices like HNSW.
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.