What problem does it solve?
Tuning LLM serving performance requires testing many combinations of context size, batch size, mmap, mlock, and speculative decoding settings, which is tedious and error-prone to do manually. This Skill guides running, debugging, and interpreting mesh-llm benchmark tune trials so you get tolerance-aware, evidence-backed configuration recommendations.
Core Features & Use Cases
- Candidate Sweeps: Sweep ctx sizes, batch/ubatch sizes, mmap/mlock values, and speculative decoding types (MTP, draft, ngram) with bounded or explicit value lists.
- JSON Evidence Collection: Capture machine-readable results including best, raw_best, pareto frontier, per-trial decode tok/s, timings, and error logs for local or SSH remote hosts.
- Tolerance-Aware Interpretation: Compare raw best versus recommended settings, explain tok/s versus context-size tradeoffs, and verify speculative decoding is actually active via debug telemetry.
- Use Case: On a remote CUDA host, run a bounded sweep over ctx sizes 8192-262144 with speculative auto mode, tee the JSON output to a timestamped file, and report the recommended configuration with its throughput and context tradeoffs.
Quick Start
Ask the assistant to run mesh-llm benchmark tune on a local GGUF model with a bounded ctx and batch sweep and interpret the JSON results.