REVIEW 2 cited by
An Efficient Inference Framework for Early-exit Large Language Models
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Building efficient inference framework has gained increasing interests for research community. Early-exit models, a variant of LLMs, improves the inference efficiency of LLMs by skipping rest layers and directly generate output tokens when they are confident enough. However, there is no work of LLM inference framework that takes early-exit models into consideration. This is non-trivial as prior art on LLM inference cannot be directly applied to early-exit models. In this work, we solves two key challenges in building efficient inference framework for early-exit models: (1) batch inference at iteration-level granularity; and (2) KV cache management. For the former, we propose to process the batch until all sequences surpass the early-exit confidence threshold. For the latter, we propose to fill the KV cache of rest layers before the iteration terminates. Our evaluation shows that, compared with the original vLLM operating at full layers, our solution achieves up to 1.25x speed up.
Forward citations
Cited by 2 Pith papers
-
Doomed from the Start: Early Abort of LLM Agent Episodes via a Recall-Controlled Probe Cascade
Hidden-state probes can flag doomed LLM-agent episodes from the first round, and a recall-calibrated cascade of abort gates cuts generated tokens by up to 60% while preserving a chosen success-recall target.
-
River-LLM: Large Language Model Seamless Exit Based on KV Share
River-LLM enables token-level early exit in decoder-only LLMs by routing exited tokens through 4-bit quantized copies of backbone layers that share the KV cache addressing scheme, achieving 1.53–2.16× wall-clock speed...
Discussion (0). Continue with ORCID to comment.