Conversation
kvark
marked this pull request as ready for review
September 19, 2026 21:24
kvark
force-pushed
the
perf/attention-autotune-2026-09-19
branch
from
September 19, 2026 22:04
050f8a3 to
37a3e52
Compare
kvark
force-pushed
the
perf/native-projection-fusion-2026-09-19
branch
from
September 19, 2026 22:04
62cc50a to
e21ed76
Compare
This was referenced Sep 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #193; ordinary command recording only.
[N,K]rows and useMatMulBT. Block formats retain their existing layout.No device/model thresholds, expanded tuning budget, precision changes, or command-buffer replay.
Matched ordinary-recording results
Source
69bbb48450fee8f9957b682ffec95733ca50c1f4; control861d87b9a85f666a5a131f82d07c0b66d9131e16includes attention tuning. Median of three fresh-process medians, with rotated engine order:Decode improves in all three trials: approximately 16% on NVIDIA and 8% on Intel. NVIDIA's new process medians span 2.475–2.748 ms; Intel's span 5.107–5.133 ms. Decode remains 1.82×/1.50× llama.cpp. CPU/GPU clocks were not fixed.
This is one SmolLM2-135M sequence with 128-token prefill and 32 cached decode steps, including full-logit host copies, not batched-throughput evidence. Both sessions visit all seven eligible tuning classes, qualify all comparisons and finish within their existing budgets. All 18 saved logit sets are finite and retain 33/33 independent CPU-reference next-token choices; this is a fixed-token numerical check, not language-quality evidence.
Protocol, ranges, preparation times and limitations.
Verification
452 CPU tests pass. The full 22-test GGUF suite and 17-test GEMV group pass on both NVIDIA and Intel, including normalized tuning, both activations/storage types, source restaging, odd f16 dimensions and a wide-vocabulary grid. All-target/all-feature Clippy, formatting and rustdoc with warnings denied pass. No new test executable or relaxed tolerance. The known Naga Workgroup ArrayStride warning remains unchanged.
CI for the measured code: all six jobs passed, including Linux coverage, macOS, Windows and MSRV. Rust host line coverage is 83.6% overall (WGSL execution is not instrumented). The final follow-up is documentation only.
No raw data or binaries in Git. The submitted paper and frozen Inferena cohort are unchanged.
Rebased after #192 merged into main. The file tree is unchanged from the pre-rebase head; the measured revisions remain on
experiment/llama-gemv-2026-09-19. Fresh post-rebase CI is running.