Sign inGet started
Paper · arXiv

Dissecting GPU Utilization for LLM Inference on Nvidia Hopper

A single SM utilization percentage can make an LLM inference workload look compute-saturated while hiding how much useful work is being done. The problem is not that the counter is wrong, but that it collapses several different mechanisms into one number. This is most severe during decode, where each request contributes only one new token and dense projection GEMMs become small-row matrix multiplications. On Hopper, the bfloat16 GMMA path executes these operations in fixed 64-row matrix fragments, so small-batch decode can fill only a small fraction of each fragment with real token rows. In this paper, we profile vLLM with FlashAttention-3 and cuBLASLt on an H100 NVL across cold prefill, ...

AuthorsMohammad Siavashi, Gerald Q. Maguire, Dejan Kostic et al.
Primary categorycs.PF
Published11 September 2026
Last updated at source11 September 2026
cs.PFcs.ARcs.DCcs.LG
Embed this entry
<iframe src="https://silytics.si/embed/item/9549b4d6-4733-4269-b35d-12f092a5ead0" width="420" height="190" style="border:0" loading="lazy" title="Silytics entry"></iframe>

Free, no tracking. More about feeds and embeds.

Silytics shows public metadata from arXiv and links to the original. Information may be incomplete or out of date. Last refreshed 17 October 2026. Licenses and terms of the original apply to the work itself. Not financial, legal or professional advice.