inference/research
verifiedhigh · 0.85updated 2026-10-04

Fast Matrix Multiplications for Lookup Table-Quantized LLMs

quantization · emnlp

Fields

id
papers/paper-flute
arXiv
2407.10960
Venue
emnlp
Venue track
findings
Year
2024
Category
quantization
Adoption
research-only
Authors
Elhoushi, Shrivastava, Liskovich, Keutzer, Bhandari
Affiliations
UC Berkeley / Amazon
Problem
Non-uniform lookup-table quantization at awkward bit widths (e.g. 3 bits) makes the dequant and matmul kernel slow, which can eat the entire bandwidth saving.
Mechanism
FLUTE is a kernel, not a format: offline RESTRUCTURING of the quantized weight matrix to minimize bit-manipulation work during unpacking, plus vectorization and DUPLICATION of the lookup table so shared-memory bandwidth is not the bottleneck. Offline restructuring is the trick - the deployment-time kernel becomes cheaper because of work done once at quantization time.
Speedup reported
Paper's own claim (abstract): at batch sizes < 32 and quantization group size 128 - the regime the paper correctly identifies as typical LLM inference - the FLUTE kernel is 2-4x FASTER THAN EXISTING GEMM KERNELS, because weight movement rather than arithmetic is the bottleneck. The compression ratio is whatever the underlying LUT format is (3-bit here); the quality cost belongs to the format, not to FLUTE. The honest reading: this is a single-sequence-decode kernel win, and the batch-size ceiling is explicit.
notes
SLUG RENAMED 2026-10-04 (parent agent): was 'flute', colliding with the quantization record of the same id, which made every bare-slug cross-reference ambiguous. Inbound refs (['scheme']) all mean the quantization record, so none needed repointing; papers are cited via `sources`, never by bare slug. arXiv ID 2407.10960 verified via /abs/. Venue EMNLP 2024 (Findings) from Semantic Scholar; year = venue year 2024. Repo already has source qlab-flute-paper and a quantization/flute record for the format. arXiv ID and title verified by fetching https://arxiv.org/abs/2407.10960 and reading the citation_title meta tag on 2026-10-03. Venue and year from the Semantic Scholar graph API batch endpoint (paper/arXiv:2407.10960) unless the record's notes say otherwise. VENUE_TRACK BACKFILL 2026-10-04 (paper-fields pass): venue_track set to 'findings' from the ACL Anthology bib index (anthology.bib, 131650 entries) by normalized title match. Evidence: anthology id 2024.findings-emnlp.724, booktitle 'Findings of the Association for Computational Linguistics: EMNLP 2024'. The Anthology id is the authoritative signal here and it is unambiguous, so this is an additive clarification of a track, not a change of venue - `venue` is untouched and no status change is implied. The reason this matters for inference readers: a Findings paper and a main-track paper at the same venue are not the same kind of evidence, and until this field existed the repo could not say which was which.

Notes

SLUG RENAMED 2026-10-04 (parent agent): was 'flute', colliding with the quantization record of the same id, which made every bare-slug cross-reference ambiguous. Inbound refs (['scheme']) all mean the quantization record, so none needed repointing; papers are cited via `sources`, never by bare slug. arXiv ID 2407.10960 verified via /abs/. Venue EMNLP 2024 (Findings) from Semantic Scholar; year = venue year 2024. Repo already has source qlab-flute-paper and a quantization/flute record for the format. arXiv ID and title verified by fetching https://arxiv.org/abs/2407.10960 and reading the citation_title meta tag on 2026-10-03. Venue and year from the Semantic Scholar graph API batch endpoint (paper/arXiv:2407.10960) unless the record's notes say otherwise.

VENUE_TRACK BACKFILL 2026-10-04 (paper-fields pass): venue_track set to 'findings' from the ACL Anthology bib index (anthology.bib, 131650 entries) by normalized title match. Evidence: anthology id 2024.findings-emnlp.724, booktitle 'Findings of the Association for Computational Linguistics: EMNLP 2024'. The Anthology id is the authoritative signal here and it is unambiguous, so this is an additive clarification of a track, not a change of venue - `venue` is untouched and no status change is implied. The reason this matters for inference readers: a Findings paper and a main-track paper at the same venue are not the same kind of evidence, and until this field existed the repo could not say which was which.

Cross-references

This record references no other records — it is a leaf. It is cited by 0.