LLMBOTTLENECK.COM

Can the NVIDIA Rubin run Inkling-Small?

Inkling-Small · NVIDIA Rubin · 8,192 ctx · whole model residentQ8_0 sizesize rangeSpeedestimate

IT FITS

Yes. 8 of 9 formats evaluated fit in 288 GB, at 8,192 tokens. No published file exists for this pair, so every size is rebuilt from the pinned architecture. The best quality that fits is Q8_0, needing 285.0 GB and running at an estimated 1350 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.

8/9formats that fit
288 GBdevice memory
285.0 GBneeded at best quality
~1350tokens per second, estimatedFaster than you read
22000GB/s bandwidth

How long a conversation. At Q8_0, this pair holds 25,510 tokens of context — roughly 19,133 words — needing 288.0 GB. Past that the NVIDIA Rubin runs out of memory, not the model out of context. This is the wall a long chat hits after it has already loaded fine. The nearest round setting below it is 16,384.

Every format evaluated

No published file exists for this pair, so every size is rebuilt from the pinned architecture. The Basis column says which is which for each row. Decode and first-token figures are calibrated estimates, not runs on this card.

FormatNeedsOf 288 GBFitsDecodeFirst tokenBasis
FP16534.4 GB186%short by 246.4 GBdoes not run—size range
Q8_0285.0 GB99%yes~1350 tok/sno comparable peaksize range
Q6_K220.6 GB77%yes~1677 tok/sno comparable peaksize range
Q5_K_M192.2 GB67%yes~1871 tok/sno comparable peaksize range
Q5_0187.8 GB65%yes~1908 tok/sno comparable peaksize range
Q4_K_M165.5 GB57%yes~2100 tok/sno comparable peaksize range
Q4_0157.0 GB55%yes~2191 tok/sno comparable peaksize range
Q3_K_M135.2 GB47%yes~2414 tok/sno comparable peaksize range
Q2_K107.5 GB37%yes~2900 tok/sno comparable peaksize range

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.
Change anything

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 Rubin runs

Where these numbers come from

Inkling-Small’s architecture is read from its publisher’s own config.json at a pinned revision, and the NVIDIA Rubin’s 288 GB and 22000 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

As JSON, from the API
curl -s https://llmbottleneck.com/v1/analyze \
  -H "Authorization: Bearer $LLMB_KEY" -H "content-type: application/json" \
  -d '{"model":"thinkingmachines-inkling-small","quantization":"Q8_0","context":8192,"hardware":"nvidia-rubin"}'

Same engine, same evidence, every field sourced. Free key in one step →

On your page, as a widget
<script src="https://llmbottleneck.com/widget.js"
  data-model="thinkingmachines-inkling-small" data-quantization="Q8_0"
  data-hardware="nvidia-rubin" data-context="8192"></script>

No key needed. Unbranded, with your own buy button, on Pro and Business →

llmbottleneck
catalogue 2026-10-03models 327devices 135