Can LFM2 24B run on NVIDIA H200 141GB?

YES — Runs Great

A80Great
Estimated from fit model

LFM2 24B needs ~32.4 GB VRAM. NVIDIA H200 141GB has 141.0 GB. With Q4_K_M quantization, expect ~296 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: HighStack: BasicBottleneck: Balanced
Share:

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 32.4 GB, 296.1 tok/s, Runs well
32.4 GB required141.0 GB available
23% VRAM used

Fit status

Runs well

Decode

296.1 tok/s

TTFT

654 ms

Safe context

131K

Memory

32.4 GB / 141.0 GB

Memory breakdown

Weights14.6 GB
KV Cache2.4 GB
Runtime1.2 GB
Headroom14.1 GB

See how fast it feels

See how fast it feelsLFM2 24B on NVIDIA H200 141GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort: def quicksort(arr): if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) # Example usage numbers = [3, 6, 8, 10, 1, 2, 1] print(quicksort(numbers)) # [1, 1, 2, 3, 6, 8, 10] The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]: """Sort a list using the quicksort algorithm. Args: arr: List of integers to sort. Returns: A new sorted list. """ if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 296.1 tok/s decode · 654ms TTFT (warm) · 740 tok/s prefill

What limits this setup

This setup is broadly balanced for this model.

No major red flags

This recommendation has enough memory headroom and acceptable estimated speed for the selected workload.

Best improvement path

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatARuns well296.1 tok/s357 ms131K
CodingARuns well296.1 tok/s654 ms131K
Agentic CodingARuns well296.1 tok/s951 ms131K
ReasoningARuns well296.1 tok/s773 ms131K
RAGARuns well296.1 tok/s1189 ms131K

Inference speed

LFM2 24B inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for LFM2 24B at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~88 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.

GPU / MacMemoryQuantSpeed (tok/s)Fits?
NVIDIARTX 5090 32GB
32 GBQ4_K_M88.2Fits
NVIDIARTX 4090 24GB
24 GBQ4_K_M56.3Tight
RX 7900 XTX 24GB
24 GBQ4_K_M50.8Tight
NVIDIARTX 3090 24GB
24 GBQ4_K_M48.1Tight
Mac Studio M3 Ultra 256GB
256 GBQ4_K_M40.9Fits
MacBook Pro M4 Max 128GB
128 GBQ4_K_M36.8Fits
MacBook Pro M4 Max 64GB
64 GBQ4_K_M36.8Fits
Mac Studio M2 Ultra 128GB
128 GBQ4_K_M34.1Fits
Mac Studio M1 Ultra 128GB
128 GBQ4_K_M32.3Fits
MacBook Pro M4 Pro 48GB
48 GBQ4_K_M23.2Fits
NVIDIARTX 4080 Super 16GB
16 GBQ4_K_M21.3Too big
MacBook Pro M3 Max 64GB
64 GBQ4_K_M17.6Fits
MacBook Pro M1 Max 64GB
64 GBQ4_K_M16.2Fits
NVIDIARTX 4070 12GB
12 GBQ4_K_M7.5Too big
NVIDIARTX 3060 12GB
12 GBQ4_K_M4.7Too big
NVIDIARTX 4060 8GB
8 GBQ4_K_M2.2Too big

Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.

Quantization options

How LFM2 24B (24B params) fits at each quantization level on NVIDIA H200 141GB (141.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
9.4 GB
LowA71
Q3_K_S
3
11.8 GB
LowA71
NVFP4
4
13.4 GB
MediumA71
Q4_K_M
4
14.6 GB
MediumA71
Q5_K_M
5
17.3 GB
HighA72
Q6_K
6
19.7 GB
HighA72
Q8_0
8
25.7 GB
Very HighA72
F16Best for your GPU
16
49.2 GB
MaximumA76

Get started

Copy-paste commands to run LFM2 24B on your machine.

Run

ollama run lfm2

Your hardware

More models your NVIDIA H200 141GB can run

ModelParamsGradeDecodeCapabilities
MistralDevstral 2 123B Instruct123BS58.4 tok/s
AlibabaQwen3-Coder 30B A3B Instruct30.5BS609.7 tok/s
AlibabaQwen 3.5 27B27BS264.4 tok/s
AlibabaQwen 3.6 27B27BS265.2 tok/s
AlibabaQwen 3.5 122B A10B122BS162.1 tok/s

Frequently asked questions

Can NVIDIA H200 141GB run LFM2 24B?

Yes, NVIDIA H200 141GB can run LFM2 24B with a A grade (Runs well). Expected decode speed: 296.1 tok/s.

How much VRAM does LFM2 24B need?

LFM2 24B (24B parameters) requires approximately 32.4 GB of memory with Q4_K_M quantization.

What is the best quantization for LFM2 24B?

The recommended quantization for LFM2 24B is Q4_K_M, which balances quality and memory efficiency.

What speed will LFM2 24B run at on NVIDIA H200 141GB?

On NVIDIA H200 141GB, LFM2 24B achieves approximately 296.1 tokens per second decode speed with a time-to-first-token of 654ms using Q4_K_M quantization.

Can NVIDIA H200 141GB run LFM2 24B for coding?

For coding workloads, LFM2 24B on NVIDIA H200 141GB receives a A grade with 296.1 tok/s and 131K context.

What context window can LFM2 24B use on NVIDIA H200 141GB?

On NVIDIA H200 141GB, LFM2 24B can safely use up to 131K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.

See all results for NVIDIA H200 141GBSee all hardware for LFM2 24B
Embed this result

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/lfm2-24b-on-h200-141gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: