Can granite embedding 107m multilingual run on NVIDIA B200 180GB?

YES — Runs Great

D33Poor

○Estimated from fit model

granite embedding 107m multilingual needs ~19.4 GB VRAM. NVIDIA B200 180GB has 180.0 GB. With Q4_K_M quantization, expect ~2 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: HighStack: BasicBottleneck: Memory bandwidth

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

19.4 GB required180.0 GB available

11% VRAM used

Fit status

Runs well

Decode

2.0 tok/s

TTFT

96800 ms

Safe context

25.7M

Memory

19.4 GB / 180.0 GB

Memory breakdown

Weights0.1 GB

KV Cache0.1 GB

Runtime1.2 GB

Headroom18.0 GB

See how fast it feels

See how fast it feelsgranite embedding 107m multilingual on NVIDIA B200 180GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API.

When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed.

Key benefits of running locally:
 - Full privacy: your prompts never leave your machine
 - No per-token cost or rate limits
 - Works offline once the model is downloaded
 - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb:

 Model size Q4 (4-bit) Q8 (8-bit) FP16
 7B params ~4.3 GB ~7.5 GB ~14 GB
 13B params ~7.9 GB ~13.9 GB ~26 GB
 70B params ~42.7 GB ~74.9 GB ~140 GB

Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 2.0 tok/s decode · 96.8s TTFT (warm) · 5 tok/s prefill

What limits this setup

This model fits, but memory bandwidth is the part holding decode speed back.

Throughput will feel slow

Estimated decode speed is only 2.0 tok/s, so this is more of a technical fit than a comfortable daily-driver setup.

Best improvement path

Prioritize bandwidth, not only capacity

If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	D	Runs well	2.0 tok/s	52800 ms	12.9M
Coding	D	Runs well	2.0 tok/s	96800 ms	25.7M
Agentic Coding	D	Runs well	2.0 tok/s	140800 ms	51.4M
Reasoning	D	Runs well	2.0 tok/s	114400 ms	25.7M
RAG	D	Runs well	2.0 tok/s	176000 ms	51.4M

Quantization options

How granite embedding 107m multilingual (0.10700000077486038B params) fits at each quantization level on NVIDIA B200 180GB (180.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	0.0 GB	Low	D37
Q3_K_S	3	0.1 GB	Low	D37
NVFP4	4	0.1 GB	Medium	D37
Q4_K_M	4	0.1 GB	Medium	D37
Q5_K_M	5	0.1 GB	High	D37
Q6_K	6	0.1 GB	High	D37
Q8_0	8	0.1 GB	Very High	D37
F16Best for your GPU	16	0.2 GB	Maximum	D37