Literature validates MSR grid but flags missing latency metrics

The 2022–2025 scientific literature on LLM on-device inference validates the majority of both resource/performance and device/hardware terms in the keyword matrix.

Research report · 2026-10-09 · Based on 2022–2025 peer-reviewed papers

Sections

Finding summary

The canonical throughput measure (tokens/s, tok/s), the latency family (latency, KV cache, context length), the thermal/energy cluster, and the quantization vocabulary each appear in multiple peer-reviewed papers as primary research vocabulary. The matrix's hybrid design — mixing academic benchmarking vocabulary with practitioner jargon — is well-supported. The main gap: TTFT and TPOT/ITL are the canonical latency decomposition metrics in academic benchmarking and are entirely absent from the grid.

Core resource and performance terms earn broad academic endorsement

The most throughput-specific terms in the resource axis appear with striking consistency across the literature. tokens/s and tok/s are the near-universal decode-throughput metric; PowerInfer-2, for instance, reports exactly "11.68 tokens/s" when running a 47B-parameter LLM on a smartphone (PowerInfer-2, arXiv:2406.06282), and every benchmarking paper in the survey set follows the same convention. latency is universally present but in academic papers it is almost always decomposed into phase-specific sub-metrics (see the gap analysis below). KV cache is discussed in multiple dedicated proposals for on-device compression or offloading, confirming it is both a symptom label and an active area of optimization research (MiniKV, arXiv:2411.18077; mzCache, arXiv:2609.01338). quantization and context length appear as independent variables in virtually every systematic evaluation (arXiv:2505.15030).

The thermal and energy cluster is equally well attested. thermal and throttling/throttled are named as a primary constraint in sustained-inference measurement studies: one paper documents that iPhone 16 Pro throughput falls from 40.35 tok/s to 22.56 tok/s within two inference iterations due to thermal throttling (arXiv:2603.23640). battery appears in mobile deployment papers as a user-facing metric ("20 conversations consume up to 6–25% of battery in under 15 minutes") (arXiv:2609.11940), while energy and power are used in instrumented-measurement studies reporting Joules per token or steady-state Watts (EnerInfer, arXiv:2606.23001; PELM, arXiv:2609.09662). The three are complementary: battery covers end-user perception, energy covers cumulative cost, power covers the instantaneous hardware envelope.

GGUF has completed the journey from practitioner format to academic artifact: 2024–2025 papers call it "a practical standard for portable deployment across ARM CPUs and NVIDIA GPUs" and cite its Q4_K_M sub-variant in methodology sections (arXiv:2604.24785).

Verdict: Core resource terms validated

tokens/s · tok/s · latency · KV cache · context length · quantization · thermal · throttling · throttled · battery · energy · power · RAM · GGUF all appear as primary research vocabulary in ≥2 peer-reviewed papers from 2022–2025.

Four practitioner terms serve issue mining but not academic retrieval

The matrix deliberately includes terms drawn from the symptom-seeded vocabulary principle of Islam et al. (2019), and four of those terms — VRAM, memory leak, regression, and slow/slow inference — are not found as primary vocabulary in academic papers about on-device LLM inference.

Design note — not a flaw

This is not a design flaw. The matrix's own §1 states that vocabulary is seeded from observable symptoms "in the reporter's free text before any diagnosis", following Islam et al. (2019). These terms are calibrated for GitHub issue corpora, where end users describe what they saw rather than what they measured. The practical consequence: they retrieve genuine on-device performance issues from issue trackers but will not match academic paper abstracts. The study's keyword justification section should acknowledge this asymmetry explicitly when discussing recall.

Device and hardware terms: SoC labels validated, consumer brands less prominent

The literature draws a consistent distinction between hardware architecture labels (which function as primary research subjects) and consumer brand/model names (which appear only incidentally as test-device identifiers).

NPU is validated at the highest level: it appears in conference paper titles at ASPLOS 2025 ("When NPUs Are Not Always Faster") (arXiv:2605.27435; ACM DL 10.1145/3669940.3707239). Snapdragon is named as the concrete SoC under study across benchmark papers covering the Snapdragon 8 Gen 3, 8 Gen 1, and X Elite families (arXiv:2501.14794). Apple Silicon is confirmed as a recognized hardware category analogous to "Snapdragon", appearing in paper titles explicitly benchmarking M1/M2/M4 systems (ACM DL 10.1145/3771563). Jetson and raspberry are validated as representative embedded/IoT edge testbeds across survey papers. ARM is consistently used at the ISA level, naming Cortex-A76 cores and Mali GPUs as specific research subjects.

By contrast, ios, iphone, ipad, and pixel are virtually absent as primary research terms. These terms are still justified in the matrix for GitHub issue mining — end users filing issues do name their device model — but their low coverage in academic papers limits their utility for literature-based validation.

Six terms from the literature are missing from the grid

Priority gaps identified

The absence of TTFT and TPOT/ITL is the most consequential gap: every on-device LLM benchmarking paper published since 2023 reports these two metrics, yet neither appears in the current keyword grid.

Latency decomposition vocabulary

Academic benchmarking papers for on-device LLM inference have converged on exactly two phase-specific metrics:

Both appear in paper titles, abstract result summaries, and benchmark comparison tables across MobiBench, lm-Meter, and the Characterizing Mobile SoC paper (MobiBench, arXiv:2609.13159; lm-Meter, arXiv:2510.06126; arXiv:2501.14794). The Hydra paper is titled "Phase-Aware Workload Characterization of LLM Inference" precisely because the prefill/decode distinction is the dominant structuring principle of on-device performance analysis (arXiv:2608.25053).

Note that "prefill" was added to the grid on 2026-10-10 (approved with 65% precision on llama.cpp). TTFT and TPOT/ITL remain as secondary-axis candidates for a future extension.

Memory bandwidth and footprint

The literature identifies memory bandwidth as the binding bottleneck for decode-phase throughput on every class of edge device: "LLM inference is largely memory-bound," with the Snapdragon 8 Gen 3's theoretical peak of 68 GB/s named as the hardware ceiling (arXiv:2501.14794). Memory footprint and peak DRAM are the preferred academic forms of the memory size constraint, more precise than bare RAM.

Sub-component hardware labels

Three sub-component labels used as independent research subjects are missing from the device axis:

All three would serve as secondary axis terms to improve recall for academic papers without degrading precision. The term heterogeneous (heterogeneous SoC, heterogeneous inference) also appears in multiple titles as a descriptor for combined CPU+GPU+NPU execution.

Missing termAxisEvidence levelRecommendation
TTFTResourceHigh — paper titles, abstract summariesAdd to RESOURCE axis (secondary)
TPOT / ITLResourceHigh — paper titles, benchmark tablesAdd to RESOURCE axis (secondary)
SoCDeviceHigh — primary unit of analysis in char. papersAdd to DEVICE axis (secondary)
HexagonDeviceMedium — named in ≥2 systems papersAdd to DEVICE axis (secondary)
ANEDeviceMedium — active research problemAdd to DEVICE axis (secondary)
memory bandwidthResourceHigh — discussed in every hardware char. paperConsider as secondary axis term

Three 2025 empirical SE papers scaffold the RQ taxonomy

A wave of empirical software-engineering papers published in 2025 studied bugs and issues in LLM inference engines by mining GitHub repositories — methodology that directly parallels this study.

Liu et al. (arXiv:2506.09713) — closest direct precedent

Manually labels 929 bugs across llama.cpp, MLC-LLM, vLLM, DeepSpeed, and TensorRT-LLM, achieving Cohen's κ = 0.927 on a 6-symptom × 28-root-cause taxonomy (source). Two repositories are shared with this study (llama.cpp, MLC-LLM), making it a direct comparator. Its S4 Abnormal Performance symptom category — covering excessive resource consumption and abnormal token generation latency — maps to the same phenomenon as RQ1. Liu et al. treat it as one of six symptoms (6% frequency), which likely underestimates on-device performance issues because their sample includes cloud-optimized engines where performance issues manifest differently.

Cai et al. (arXiv:2409.16559) — taxonomy with separate memory/performance categories

Studied 994 closed issues from 15 LLM open-source projects including Ollama; proposed a 15-category taxonomy where Performance Issue (7.14%) and Memory Issue (3.92%) are treated as separate top-level categories (source). The explicit separation of memory from performance as distinct top-level categories is a direct precedent for this study's resource_category field.

Chen et al. ICSE 2021 (arXiv:2101.04930) — methodological baseline

The methodological predecessor for on-device mobile inference faults specifically; collects 304 faults from TF Lite and Core ML and proposes a 23-category taxonomy (source). Should be cited as the baseline from which this study advances by covering the post-2022 generation of on-device LLM runtimes.

The standard RQ structure across all related empirical studies converges on: (1) a symptom/category taxonomy, (2) root-cause analysis, and (3) fix-effort characterization. This study's RQ1 (symptom categories) and RQ3 (quantization impact) align with this structure.

Conclusion

The keyword matrix is well-grounded in the 2022–2025 literature. The principal corrections needed are on the academic-retrieval side:

The taxonomy question is answered decisively: Liu et al. (2506.09713) and Cai et al. (2409.16559) together provide a citation-backed foundation for the RQ1 category scheme, and their separation of memory from performance validates this study's choice to do the same.