MLX-LM on 64GB Apple M4 Max: Qwen3-30B-A3B-Instruct-2507 4-bit generation throughput (128 tokens)
Fields
benchmarks/mlx-m4-max-qwen3-30b-a3b-4bit-decode-tok-sNotes
Recorded as the flagship Apple-silicon MoE decode number with unusually complete methodology for MLX, which is rare - prompt length, generation length, model repo, mlx version, mlx-lm version and OS are all stated. CONFIDENCE CAPPED AT 0.6 AND STATUS verified-from-an-unmerged-PR: this table comes from mlx-lm PR #552, which was closed WITHOUT merging in Aug 2026 by maintainer zcbenz citing review capacity. These are the MLX-LM project's own numbers (Apple-authored, hence measured_by=vendor) but they never received maintainer sign-off and are not in the merged tree. The precision sweep in the same table is the more valuable artefact than any single point: for Qwen3-30B-A3B on M4 Max, q8 = 83.16, q6 = 94.14, q5 = 101.00, q4 = 113.33 generation tok/s, with MMLU Pro falling 72.46 -> 72.41 -> 71.97 -> 70.71 and peak memory 33.46 -> 25.82 -> 22.01 -> 18.20 GB. On unified memory the decode rate rises monotonically as weights shrink, which is the expected bandwidth-bound behaviour and makes 4-bit the obvious operating point on a 64GB part. See also mlx-m4-max-qwen3-4b-fp16-prefill-tok-s for the prefill side and the 40-core question.
PROVENANCE RAISED 2026-10-08 (w8-bench-src): the unmerged-PR caveat below WAS THE REASON THIS WAS SOURCED ONLY AS A TIER-E COMMUNITY POST, and that caveat is now verified WRONG. GET /repos/ml-explore/mlx-lm/pulls/552 returns state=closed, merged=TRUE, merged_at=2025-10-15T19:24:12Z, merge_commit_sha a4c64703906f709a493341508ac31af4085d2638 - so PR #552 by awni MERGED on 15 Oct 2025. The table is not an orphan PR; it is live in the merged tree at mlx_lm/BENCHMARKS.md, fetched and read on 2026-10-08 and recorded as [[w8-src-mlxlmm-552-benchmarks-merged]], where the identical q8/q6/q5/q4 sweep appears (83.16 / 94.14 / 101.00 / 113.33 generation tok/s; MMLU Pro 72.46 / 72.41 / 71.97 / 70.71; peak memory 33.46 / 25.82 / 22.01 / 18.20 GB). VALUE UNCHANGED (113.33) AND CONFIDENCE UNCHANGED (0.6), because merged is not the same as independently reproduced: still one run per row, no trial count, no GPU-core count for the M4 Max SKU, no thermal state. WHAT CHANGED is that the figure is now attributable to a document a reader can fetch today, published by the author who wrote the harness, in the vendor org's own repository. So this record moves from Tier E to Tier A and the statement that stopped it is retired as a wrong statement about the repo's own evidence.