Who it is forA developer whose local model runs slowly on the CPU and whose GPU sits mostly idle.
The problemDefault engine settings often leave much of the model on the CPU, so throughput stays low.
The outcomeBenchmarked parameter sets for your goal (latency, throughput, or prefill), saved as default deployment parameters.
What you need first
- Python 3.9+ and Node.js 18+ on the control machine
- A target machine with llama.cpp, vLLM, or ComfyUI already installed, or installable through the tool
- Network or SSH access to any remote target you want to manage
Steps
- Run
cd backendthenpip install -r requirements.txt, thenuvicorn app.main:app --host 127.0.0.1 --port 8000 - In a second terminal, run
cd frontendthennpm install && npm run dev - Open
http://localhost:3000, go to Settings, add the local machine, and click Test connection to view hardware info - On the Tuning page, pick a goal (latency, throughput, or prefill) and run auto tuning
- Review the benchmark results and use the tuned parameters as defaults on the Deploy page
Prompt for your agent
Using the repo htobty/ReadyLLM, start the backend on 127.0.0.1:8000 and the frontend on localhost:3000, register the local machine as target <target-name>, and run auto tuning for the throughput goal. Report the benchmark results and confirm the tuned parameters are available as default deployment parameters.
Caveat. The README states the 50% speedup as a claim for one tested setup, so your gain depends on your own hardware and model.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for htobty/ReadyLLM and "Auto-tune a local LLM for faster generation"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer