LLMBOTTLENECK.COM

Can the NVIDIA A100 80GB SXM run North-Micro-Vision-Instruct?

North-Micro-Vision-Instruct · NVIDIA A100 80GB SXM · 8,192 ctx · whole model residentFP16 sizereconstructed sizeSpeedestimate

IT FITS

Yes. 9 of 9 formats evaluated fit in 80 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 FP16, needing 6.36 GB and running at an estimated 309 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
80 GBdevice memory
6.36 GBneeded at best quality
~309tokens per second, estimatedFaster than you read
2039GB/s bandwidth

How long a conversation. At FP16, this pair holds 500,000 tokens of context — roughly 375,000 words — needing 20.5 GB. That is CohereLabs's own configured maximum of 500,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 262,144.

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 80 GBFitsDecodeFirst tokenBasis
FP166.36 GB8%yes~309 tok/s~1.1 sreconstructed size
Q8_04.04 GB5%yes~522 tok/s~1.1 sreconstructed size
Q6_K3.44 GB4%yes~634 tok/s~1.1 sreconstructed size
Q5_K_M3.20 GB4%yes~684 tok/s~1.1 sreconstructed size
Q5_03.18 GB4%yes~694 tok/s~1.1 sreconstructed size
Q4_K_M2.99 GB4%yes~739 tok/s~1.1 sreconstructed size
Q4_02.93 GB4%yes~761 tok/s~1.1 sreconstructed size
Q3_K_M2.76 GB3%yes~808 tok/s~1.1 sreconstructed size
Q2_K2.52 GB3%yes~904 tok/s~1.1 sreconstructed size

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 A100 80GB SXM runs

Where these numbers come from

North-Micro-Vision-Instruct’s architecture is read from its publisher’s own config.json at a pinned revision, and the NVIDIA A100 80GB SXM’s 80 GB and 2039 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":"coherelabs-north-micro-vision-instruct","quantization":"FP16","context":8192,"hardware":"nvidia-a100-80gb-sxm"}'

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="coherelabs-north-micro-vision-instruct" data-quantization="FP16"
  data-hardware="nvidia-a100-80gb-sxm" data-context="8192"></script>

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

llmbottleneck
catalogue 2026-10-03models 327devices 135