tune

Benchmark local hardware to tune embedding and Qdrant configuration parameters.

11|3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill tune-artk0de
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tune
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude-plugin/tea-rags-setup/skills/tune
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill tune-artk0de

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the guesswork in configuring TeaRAGs by benchmarking your specific hardware to find the optimal throughput and concurrency settings.

Core Features & Use Cases

  • Hardware Benchmarking: Automatically tests embedding throughput, Qdrant storage speed, and pipeline concurrency.
  • Configuration Management: Saves optimal performance parameters directly to your setup progress file for seamless MCP integration.
  • Use Case: After installing TeaRAGs, run this skill to ensure your local embedding provider and vector database are tuned for maximum speed, preventing slow indexing on large codebases.

Quick Start

Ask the agent to benchmark your hardware and tune the performance parameters for your current setup.

Frequently Asked Questions about tune

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize TeaRAGs performance for my local hardware?

To optimize TeaRAGs performance, you can run hardware benchmarking to stress test embedding throughput and Qdrant storage latency, which automatically generates tuned concurrency and batching configuration parameters for your specific setup.

Why is indexing slow on my large codebase with TeaRAGs?

Indexing is slow because default concurrency and batching values may not match your hardware. Running a hardware benchmark calibrates your local embedding provider and Qdrant daemon to determine optimal throughput settings, preventing slow indexing.

How does hardware benchmarking work for vector database configuration?

Hardware benchmarking works by executing stress tests on embedding throughput and storage latency to calibrate system-specific concurrency and batching values. This process generates a tuned environment configuration for seamless MCP integration.

What are the limitations of benchmarking embedding throughput locally?

Benchmarking embedding throughput requires a local Qdrant daemon and the tea-rags CLI to be accessible. If local hardware resources are heavily constrained, the generated concurrency and batching values will reflect those hardware limitations in the tuned configuration.

Can I tune Qdrant storage latency without manual configuration?

You can tune Qdrant storage latency without manual configuration by executing automated stress tests. This benchmarks your local hardware and saves the optimal performance parameters directly to your setup progress file for immediate use.