Who it is forA developer who already runs llama.cpp, LM Studio, vLLM, SGLang, or Ollama locally and wants to know how fast it serves agent-style requests.
The problemChat tests do not show how a server handles long agent conversations where every request carries the full history.
The outcomeA results directory with summary.json holding output tokens per second and median and p95 first-token and turn times.
What you need first
- uv installed (it fetches Python 3.12 if needed)
- A model server you already run with an OpenAI-compatible API, or a framework the tool can start (llama.cpp, vLLM, SGLang, or Splash on Apple Silicon)
- For full results, a server or device that can run a 65,536-token context at batch size 1
- Docker only if you want live tool calling
Steps
- Install the tool with
uv tool install agentperf-local - Start your model server and note its base URL and model name, for example http://127.0.0.1:8080/v1 for llama.cpp
- Run
agentperf-local run --base-url http://127.0.0.1:8080/v1 --model served-model --output-dir results/my-server(inferred, check the README) - Open results/my-server/summary.json and read the headline numbers
Prompt for your agent
Using the agentperf-local repo from ArtificialAnalysis, run `agentperf-local run` against the OpenAI-compatible server at <base-url> serving model <model-name>, writing output to results/<name>. Confirm that summary.json exists and report output tokens per second and median and p95 turn times. Verify the run is not marked reduced before you report it as comparable.
Caveat. The exact output policy sends ignore_eos, and the tool stops if your server does not honor it. Ollama cannot honor it, so Ollama results use the recorded policy and are not directly comparable.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page