Can Command A 111B run on NVIDIA H200 PCIe 141GB?

YES — Runs Great

S94Excellent

○Estimated from fit model

Command A 111B needs ~86.6 GB VRAM. NVIDIA H200 PCIe 141GB has 141.0 GB. With Q4_K_M quantization, expect ~60 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: HighStack: StandardBottleneck: Balanced

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) — 86.6 GB, 65.0 tok/s, Runs well

86.6 GB required141.0 GB available

61% VRAM used

Fit status

Runs well

Decode

65.0 tok/s

TTFT

2978 ms

Safe context

239K

Memory

86.6 GB / 141.0 GB

Memory breakdown

Weights67.7 GB

KV Cache3.9 GB

Runtime0.9 GB

Headroom14.1 GB

See how fast it feels

See how fast it feelsCommand A 111B on NVIDIA H200 PCIe 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: 65.0 tok/s decode · 3.0s TTFT (warm) · 163 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

Workload	Grade	Fit	Decode	TTFT	Context
Chat	S	Runs well	59.5 tok/s	1773 ms	239K
Coding	S	Runs well	59.5 tok/s	3251 ms	239K
Agentic Coding	S	Runs well	59.5 tok/s	4729 ms	239K
Reasoning	S	Runs well	59.5 tok/s	3842 ms	239K
RAG	S	Runs well	59.5 tok/s	5911 ms	239K

Quantization options

How Command A 111B (111B params) fits at each quantization level on NVIDIA H200 PCIe 141GB (141.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	43.3 GB	Low	A83
Q3_K_S	3	54.4 GB	Low	A85
NVFP4	4

Get started

Copy-paste commands to run Command A 111B on your machine.

Run

ollama run command-a

Your hardware

More models your NVIDIA H200 PCIe 141GB can run

Model	Params	Grade	Decode	Capabilities
👁 Mistral Devstral 2 123B Instruct	123B	S	58.4 tok/s
👁 Alibaba Qwen 3.5 122B A10B	122B	S

Frequently asked questions

See all results for NVIDIA H200 PCIe 141GB See all hardware for Command A 111B

URL: https://willitrunai.com/can-run/command-a-111b-on-h200-pcie-141gb

⇱