Muse Glimmer on one Arc Pro B70

New: 840.8 aggregate tok/s at C96 in an experimental burst sweep

The highest observed median was 840.810 aggregate completion tok/s at C96
with DFlash K3 and a frozen 32k draft vocabulary shortlist. This is a
short-prefill, repeated-prompt, 256-token reasoning-only burst measurement—
not per-stream decode, continuous traffic, long-context throughput, or a
completed-answer score. C48 (794.194 tok/s) is the workload-specific
throughput/latency knee, not a production recommendation.

C8–C128 table, graph, artifact, method, and limits →

Retained C8/K4 native-context profile

The published GPTQ + XPU graphs + DFlash K4 profile delivers 278.1
aggregate e2e tok/s across eight clients on its matched 256-output-token
workload—5.8× the original C1/K20 scheduler under the same load. It is a
different draft-head/configuration from the experimental shortlist/K3 sweep.

Native 131,072-token prompt-plus-output context works. We verified eight
resident ~64k prompts, staggered queue admission/drain, and six ordinary ~129k
requests served correctly through the queue. Known limit: a near-capacity,
forced-length six-request test produced two empty responses; that failure remains
unresolved. This is a research profile, not an unrestricted production-safety
claim.

C8/K4 configuration, full numbers, reproduction, and limitations →

Original C1 completed-answer results

Public numbers for Meta’s Muse Glimmer 30B on a single Intel Arc Pro B70 have lived in the high 20s. The best documented llama.cpp recipe — SergiioB’s B70 cookbook — is 26.8 tok/s median decode (28.9 peak) at 128k context with DFlash n_max=2. We ran that class of config on the same card and landed in the same place.

Then we changed stack. Same GPU, vLLM-XPU, GPTQ W4A16, XPU graphs, and a 20-token DFl