← TinyGPT · docs · devlog · roadmap · speedup
source: docs/research/inference_benchmarks_may_2026.md · view on GitHub ↗

State of LLM Inference Benchmarks (May 2026)

Research compiled by an Explore subagent on 2026-05-29 to cover the gap between my Jan 2026 knowledge cutoff and current state. Includes URLs for verification.

1. Suite landscape

2. Apple Silicon specifically

There is no MLPerf-equivalent for M-series yet — this is a real gap. The closest credible artifacts:

3. Metrics that matter

Standard set to report: TTFT, ITL/TPOT, decode tok/s at batch=1/4/16/64, prefill tok/s, peak RSS + unified memory high-water mark, sustained tok/s under thermal load (Mac-specific!), energy per output token (J/tok) via powermetrics, model coverage matrix (dense + MoE + quantization). Long-context: report at 4k/32k/128k/1M with cache-hit and cache-miss separately.

4. Reproducibility bar

For “we beat X by Y%” to survive review: pin exact engine commit hashes, model SHA, quantization scheme, KV-cache dtype, seed, sampling params (temp, top-p), prompt corpus (ShareGPT-v3 or LMSYS-Chat-1M are conventional), batch/concurrency profile, hardware SKU + RAM tier + macOS build + thermal state (cold vs steady-state, ambient temp), ≥3 runs report median + p95/p99. MLPerf-style submitter README + log replay is the gold bar. Bench360 ships YAML configs you can copy.

5. Publishable gaps

Real opportunities — none of these are well-measured publicly as of May 2026:

  1. ANE utilization during serving — no public benchmark reports ANE residency %, ANE↔GPU handoff latency, or ANE energy/token. Orion is a proof-of-concept, not a benchmark.
  2. Energy/token on Apple Silicon — TokenPowerBench is NVIDIA-only; Bench360’s energy module doesn’t cover unified-memory powermetrics semantics.
  3. Prompt-cache hit-rate-dependent TTFT on-device — production servers report ~90% KV-cache hit rates (llm-d data); no Mac suite varies hit-rate as an axis.
  4. Sustained vs burst — fan-curve / thermal-throttle behavior over 10-minute serving windows.
  5. MoE on unified memory — expert-cache thrash on M-series is unmeasured (arXiv 2604.18788 on MoE+NPU is the closest).

Sources