Skip to content
Skills Library
DevOps & cloud · Planning

qdrant-performance-optimization

/qdrant-performance-optimization

Navigation hub linking sub-skills for proactive Qdrant tuning: search speed, indexing performance, and memory usage optimization. Use when planning configuration or capacity changes to improve speed and efficiency. For diagnosing an active production slowdown or analyzing live metrics, use qdrant-monitoring instead.

Repository
skills ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

81/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content16 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Navigation hub linking sub-skills for proactive Qdrant tuning: search speed, indexing performance, and memory usage optimization. Use when planning configuration or capacity changes to improve speed and efficiency. For diagnosing an active production slowdown or analyzing live metrics, use qdrant-monitoring instead.

Original author description

Navigation hub linking sub-skills for proactive Qdrant tuning: search speed, indexing performance, and memory usage optimization. Use when planning configuration or capacity changes to improve speed and efficiency. For diagnosing an active production slowdown or analyzing live metrics, use qdrant-monitoring instead.

How it works

SKILL.md has no level-two headings · 24 lines, 196 words

SKILL.md preview
---
name: qdrant-performance-optimization
description: "Navigation hub linking sub-skills for proactive Qdrant tuning: search speed, indexing performance, and memory usage optimization. Use when planning configuration or capacity changes to improve speed and efficiency. For diagnosing an active production slowdown or analyzing live metrics, use qdrant-monitoring instead."
allowed-tools:
  - Read
  - Grep
  - Glob
---


# Qdrant Performance Optimization

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.
Files in this package (4)
  • SKILL.md 2 KB
  • indexing-performance-optimization/SKILL.md 4 KB
  • memory-usage-optimization/SKILL.md 8 KB
  • search-speed-optimization/SKILL.md 6 KB

Versions

RepositoryScoreLicence
This page · qdrant/skills81Apache-2.0
github/awesome-copilot85MIT

Database snapshot: 13.11.2026 · package version 9f67cf94ec5e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 85qdrant-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…
  • 85qdrant-indexing-performance-optimization
    Diagnoses and fixes slow Qdrant indexing and data ingestion. Use when someone reports 'uploads are slow', 'indexing takes forever', 'optimizer is stuck', 'HNSW build time too long', or 'data uploaded but search is bad'. Also use when optimizer status shows errors, segments won't…
  • 100grepai-storage-qdrant
    Configure Qdrant vector database for GrepAI. Use this skill for high-performance vector search.
  • 90qdrant-deployment-options
    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…
  • 85qdrant-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…
  • 100tune
    Benchmark this hardware and write optimal performance parameters (embedding throughput, Qdrant storage, pipeline concurrency, git trajectory) into ~/.tea-rags/setup-progress.json. Triggers on "indexing is slow", "tune performance", "benchmark my hardware", "find optimal batch…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.