Can the NVIDIA H100 80GB SXM run granite-4.1-30b?
IT FITS
Yes. 9 of 9 formats evaluated fit in 80 GB, at 8,192 tokens. Every row is sized from a published file. The best quality that fits is FP16, needing 60.7 GB and running at an estimated 38 tokens per second.
Fitting in memory is not the same as loading. Whether the runtime and version you have supports this architecture and format on this machine has not been tested here.
How long a conversation. At FP16, this pair holds 81,878 tokens of context — roughly 61,409 words — needing 80.0 GB. Past that the NVIDIA H100 80GB SXM runs out of memory, not the model out of context, which would allow 131,072. This is the wall a long chat hits after it has already loaded fine. The nearest round setting below it is 65,536.
Every format evaluated
Every row is sized from a published file. The Basis column says which is which for each row. Decode and first-token figures are calibrated estimates, not runs on this card.
| Format | Needs | Of 80 GB | Fits | Decode | First token | Basis |
|---|---|---|---|---|---|---|
| FP16 | 60.7 GB | 76% | yes | ~38 tok/s | no comparable peak | published data |
| Q8_0 | 33.6 GB | 42% | yes | ~69 tok/s | no comparable peak | published data |
| Q6_K | 26.6 GB | 33% | yes | ~88 tok/s | no comparable peak | published data |
| Q5_K_M | 23.4 GB | 29% | yes | ~101 tok/s | no comparable peak | published data |
| Q5_0 | 22.9 GB | 29% | yes | ~103 tok/s | no comparable peak | published data |
| Q4_K_M | 20.4 GB | 26% | yes | ~116 tok/s | no comparable peak | published data |
| Q4_0 | 19.3 GB | 24% | yes | ~123 tok/s | no comparable peak | published data |
| Q3_K_M | 16.9 GB | 21% | yes | ~138 tok/s | no comparable peak | published data |
| Q2_K | 13.7 GB | 17% | yes | ~179 tok/s | no comparable peak | published data |
Sized at 8,192 tokens of context with the whole model resident — weights, the KV cache and the runtime reserve, offload off. Speed is only quoted for a format that fits: a rate for a configuration that cannot load is not a fact about anything.
Why the first-token figure is the same on every row
First token is modelled from the arithmetic the prompt requires, and that count does not change with the weight format — which is why it reads the same on every row. Real prefill does vary by format, because a quantized matmul is a different kernel; this model does not capture that, and the figure should be read as an order of magnitude rather than a ranking between formats.
What the labels mean
- published data
- Read from a published source — a file's byte count, a model's configuration or a manufacturer's specification — or exact arithmetic on such values. Not a measurement on a machine.
- reconstructed size
- Weight size reconstructed from the pinned architecture, because no published file exists.
- size range
- Only a lower and an upper bound are claimed for this weight size.
- estimate
- Calculated from sourced inputs by a stated method; an estimate, not a measurement.
This page fixes the context at 8,192 tokens and one device. Batch, concurrent users, KV-cache format, clusters and rental cost are all in the calculator, already set to this pairing.
Open in the calculator →Everything the NVIDIA H100 80GB SXM runs
granite-4.1-30b’s architecture is read from its publisher’s own config.json at a pinned revision, and the NVIDIA H100 80GB SXM’s 80 GB and 3350 GB/s come from the manufacturer’s specification. How far each figure can be trusted is published, per format and worst case included, on the accuracy scorecard.
Building this into your own product? A free API key returns exactly these figures, and the widget puts this answer on a product page with one script tag.
Use this answer in your own product
curl -s https://llmbottleneck.com/v1/analyze \
-H "Authorization: Bearer $LLMB_KEY" -H "content-type: application/json" \
-d '{"model":"ibm-granite-granite-4-1-30b","quantization":"FP16","context":8192,"hardware":"nvidia-h100-80gb-sxm"}'Same engine, same evidence, every field sourced. Free key in one step →
<script src="https://llmbottleneck.com/widget.js" data-model="ibm-granite-granite-4-1-30b" data-quantization="FP16" data-hardware="nvidia-h100-80gb-sxm" data-context="8192"></script>
No key needed. Unbranded, with your own buy button, on Pro and Business →