Who it is forA Mac owner with an M3 or newer chip on macOS 26.4 or later who wants to measure Splash performance.
The problemServing a large model on a Mac with a custom engine means pinning versions and model snapshots so results can be compared.
The outcomeA results directory for the Splash recipe, with the snapshot verified and the run using the exact output policy.
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 Splash engine with
brew install incoai/tap/splash - Install the tool with
uv tool install agentperf-local - Run
agentperf-local managed-run --profile-id qwen38-27b-splash-dflash --framework splash --output-dir results/qwen38-splash(inferred, check the README) - Read summary.json in results/qwen38-splash
Prompt for your agent
Using the agentperf-local repo from ArtificialAnalysis, run `agentperf-local managed-run` with --profile-id qwen38-27b-splash-dflash and --framework splash, writing to results/<name>. Expect summary.json in that directory. Verify that the recipe ran the exact policy and that the KV cache was eight-bit before reporting numbers.
Caveat. The recipe needs an M3 or newer Mac on macOS 26.4 or later, so it will not run on other hardware.
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