Phase 6
Populated context, KV placement, and reference comparisons.
Read complete source ↗Selected reported results, not a universal speed claim. Every row below belongs to a specific model, workload, and decoding configuration.
Source: Phase 6.6.1 tables in the report snapshot at 140f6f7. Engine change:
c7c8c79; earlier Phase 6.6: ed7a5db. GEXEC active, CPU expert
path, max draft 4, greedy generation. Qwen cross-window parity runs use GUILD_IQ_MT_MIN=1.
These are decode tokens per second, not end-to-end request throughput. Ranges combine reported development runs and revisions; they are not confidence intervals or paired median/dispersion estimates.
GEXEC artifacts were regenerated during tuning. Exact per-row calibration identity is not established here, limiting controlled cross-revision comparisons.
| Model / quantization | Workload | Prompt / gen | Normal | Fixed strategy | Adaptive | Source |
|---|---|---|---|---|---|---|
Ornith 1.5 35B Q4_K_M | W2 · Summarization | 256 / 128 | 50.27 | Lookup · 82.19 | 80.08–80.84 | §8.3 A ↗ |
Ornith 1.5 35B Q4_K_M | W7 · Creative prose | 256 / 128 | 49.75 | Lookup · 48.84 | 49.10–49.18 | §8.3 A ↗ |
Qwen3.8-Flash-Next UD-IQ4_XS | W3 · JSON schema | 256 / 64 | 18.33 | MTP · 23.43 | 23.52 | §8.3 B ↗ |
Qwen3.8-Flash-Next UD-IQ4_XS | W8 · Mathematical reasoning | 256 / 64 | 18.40 | MTP · 23.94 | 23.68 | §8.3 B ↗ |
Favorable input/output overlap. Fixed lookup is faster in the reported results.
Adaptive remains below normal. Fallback does not guarantee zero regression.
Development result; the small difference from fixed MTP is not a demonstrated statistically significant win.
Phase 6.6 adaptive was 24.31 tok/s. This Phase 6.6.1 result regresses versus that revision and fixed MTP.
80+ tok/s Ornith results rely on favorable speculative workloads with substantial reusable text. They are not general chat throughput, all-model performance, or measurements on a small-RAM consumer desktop.
Offline calibration measures CPU dispatch and lookup/retrieval microbenchmarks. Full verification curves, GPU/context costs, and concurrent-session scaling still include estimates. A doubled CPU job count is not a concurrent-session benchmark.
The website does not assert successful Phase 6.6.1 sanitizer, complete CUDA CTest, seeded-sampling, or concurrency validation without retained evidence. The engine report is available as a historical source, with those limits noted.
Ryzen 5 5600X / RTX 5070 results remain pending actual hardware measurement.
Populated context, KV placement, and reference comparisons.
Read complete source ↗CPU expert kernels, prefill, and end-to-end optimization.
Read complete source ↗Adaptive decoding, calibration, reported workloads, and held-out cases.
Read complete source ↗