LLMBOTTLENECK.COM

Can the NVIDIA Rubin run LFM2.5-230M?

LFM2.5-230M · NVIDIA Rubin · 8,192 ctx · whole model residentFP16 sizesize rangeSpeedestimate

IT FITS

Yes. 9 of 9 formats evaluated fit in 288 GB, at 8,192 tokens. 4 of them are sized from a published file; the rest are rebuilt from the pinned architecture. The best quality that fits is FP16, needing 1.36 GB and running at an estimated 27501 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.

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

How long a conversation. At FP16, this pair holds 128,000 tokens of context — roughly 96,000 words — needing 2.83 GB. That is LiquidAI's own configured maximum of 128,000 tokens, not the card running out. A larger device does not extend it; a documented RoPE or YaRN extension might, and is a separate question from this one. The nearest round setting below it is 65,536.

Every format evaluated

4 of them are sized from a published file; the rest are 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
FP161.36 GB0%yes~27501 tok/sno comparable peaksize range
Q8_01.15 GB0%yes~44481 tok/sno comparable peakpublished data
Q6_K1.09 GB0%yes~52922 tok/sno comparable peakpublished data
Q5_K_M1.07 GB0%yes~56518 tok/sno comparable peakpublished data
Q5_01.06 GB0%yes~57058 tok/sno comparable peaksize range
Q4_K_M1.05 GB0%yes~60379 tok/sno comparable peakpublished data
Q4_01.03 GB0%yes~61589 tok/sno comparable peaksize range
Q3_K_M1.02 GB0%yes~64868 tok/sno comparable peaksize range
Q2_K0.99 GB0%yes~70830 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

LFM2.5-230M’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":"liquidai-lfm2-5-230m","quantization":"FP16","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="liquidai-lfm2-5-230m" data-quantization="FP16"
  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