qdrant-minimize-latency by github

Decision brief

What it does—and where it fits

Latency of a single query is determined by the slowest component in the query execution path. It is sometimes correlated with throughput, but not always — throughput and latency are opposite tuning directions.

Best for

Use when someone asks 'search is slow', 'how to reduce latency', 'p99 is too high', 'tail latency', 'single query too slow', 'how to make search faster', or 'latency spikes'.

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/github/awesome-copilot --skill "skills/qdrant-scaling/minimize-latency"

Safe inspection promptEditorial

Inspect the Agent Skill "qdrant-minimize-latency" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/qdrant-scaling/minimize-latency/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
Performance Tuning for Lower Latency
Increase segment count to match CPU cores (defaultsegmentnumber: 16) Minimizing latency
Increase segment count to match CPU cores (defaultsegmentnumber: 16) Minimizing latencyKeep quantized vectors and HNSW in RAM (alwaysram=true)Reduce hnswef at query time (trade recall for speed) Search params
02
Memory Pressure and Latency
RAM is the most critical resource for latency. If working set exceeds available RAM, OS cache eviction causes severe, sustained latency degradation.
Vertical scale RAM first. Critical if working set 80%.Use quantization: scalar (4x reduction) or binary (16x reduction) QuantizationMove payload indexes to disk if filtering is infrequent On-disk payload index
03
Vertical Scaling for Latency
More RAM and faster CPU directly reduce latency. See Vertical Scaling for node sizing guidelines.
More RAM and faster CPU directly reduce latency. See Vertical Scaling for node sizing guidelines.
04
What NOT to Do
Do not expect to optimize latency and throughput simultaneously on the same node
Do not expect to optimize latency and throughput simultaneously on the same nodeDo not use few large segments for latency-sensitive workloads (each segment takes longer to search)Do not run at 90% RAM (cache eviction causes severe latency degradation that can last days)

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	68/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	37,126	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: github/awesome-copilot
Skill path: skills/qdrant-scaling/minimize-latency/SKILL.md
Commit: 9933dcad5be5caeb288cebcd370eeeb2fc2f1685
License: MIT
Collected: 2026-07-28
Default branch: main

View the original SKILL.md

Scaling for Query Latency

Latency of a single query is determined by the slowest component in the query execution path. It is sometimes correlated with throughput, but not always — throughput and latency are opposite tuning directions.

Low latency optimization is aimed at utilising maximum resource saturation for a single query, while throughput optimization is aimed at minimizing per-query resource usage to allow more parallel queries.

Performance Tuning for Lower Latency

Increase segment count to match CPU cores (default_segment_number: 16) Minimizing latency
Keep quantized vectors and HNSW in RAM (always_ram=true)
Reduce hnsw_ef at query time (trade recall for speed) Search params
Use local NVMe, avoid network-attached storage

Memory Pressure and Latency

RAM is the most critical resource for latency. If working set exceeds available RAM, OS cache eviction causes severe, sustained latency degradation.

Vertical scale RAM first. Critical if working set >80%.
Use quantization: scalar (4x reduction) or binary (16x reduction) Quantization
Move payload indexes to disk if filtering is infrequent On-disk payload index
Set optimizer_cpu_budget to limit background optimization CPUs
Schedule indexing: set high indexing_threshold during peak hours

Vertical Scaling for Latency

More RAM and faster CPU directly reduce latency. See Vertical Scaling for node sizing guidelines.

What NOT to Do

Do not expect to optimize latency and throughput simultaneously on the same node
Do not use few large segments for latency-sensitive workloads (each segment takes longer to search)
Do not run at >90% RAM (cache eviction causes severe latency degradation that can last days)
Do not ignore optimizer status during performance debugging
Do not scale down RAM without load testing (cache eviction causes days-long latency incidents)