인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
생산성 및 협업 · SKILL.md

vector-index-tuning

vector-index-tuning

Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: vector-index-tuning description: "Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure." risk: safe source: community date_added: "2026-02-27"

Vector Index Tuning

Guide to optimizing vector indexes for production performance.

Use this skill when

  • Tuning HNSW parameters
  • Implementing quantization
  • Optimizing memory usage
  • Reducing search latency
  • Balancing recall vs speed
  • Scaling to billions of vectors

Do not use this skill when

  • You only need exact search on small datasets (use a flat index)
  • You lack workload metrics or ground truth to validate recall
  • You need end-to-end retrieval system design beyond index tuning

Instructions

  1. Gather workload targets (latency, recall, QPS), data size, and memory budget.
  2. Choose an index type and establish a baseline with default parameters.
  3. Benchmark parameter sweeps using real queries and track recall, latency, and memory.
  4. Validate changes on a staging dataset before rolling out to production.

Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Safety

  • Avoid reindexing in production without a rollback plan.
  • Validate changes under realistic load before applying globally.
  • Track recall regressions and revert if quality drops.

Resources

  • resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
저장한 Skills