embeddinggemma 300M needs ~20.3 GB VRAM. H100 NVL 188GB has 188.0 GB. With Q6_K quantization, expect ~4 tok/s.
Operating mode
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.
Select quantization to explore
Fit status
Runs well
Decode
4.2 tok/s
TTFT
46095 ms
Safe context
26.8M
Memory
20.3 GB / 188.0 GB
This model fits, but memory bandwidth is the part holding decode speed back.
Throughput will feel slow
Estimated decode speed is only 4.2 tok/s, so this is more of a technical fit than a comfortable daily-driver setup.
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.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | D | Runs well | 4.2 tok/s | 25143 ms | 13.4M |
| Coding | D | Runs well | 4.2 tok/s | 46095 ms | 26.8M |
| Agentic Coding | D | Runs well | 4.2 tok/s | 67048 ms | 53.7M |
| Reasoning | D | Runs well | 4.2 tok/s | 54476 ms | 26.8M |
| RAG | D | Runs well | 4.2 tok/s | 83810 ms | 53.7M |
How embeddinggemma 300M (0.30000001192092896B params) fits at each quantization level on H100 NVL 188GB (188.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 0.1 GB | Low | D37 |
Q3_K_S | 3 | 0.1 GB | Low | D37 |
NVFP4 | 4 |
Copy-paste commands to run embeddinggemma 300M on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "ggml-org/embeddinggemma-300M-GGUF" \
--hf-file "embeddinggemma-300M-GGUF-Q6_K.gguf" \
-c 4096 -ngl 99Yes, H100 NVL 188GB can run embeddinggemma 300M with a D grade (Runs well). Expected decode speed: 4.2 tok/s.
embeddinggemma 300M (0.30000001192092896B parameters) requires approximately 20.3 GB of memory with Q6_K quantization.
The recommended quantization for embeddinggemma 300M is Q6_K, which balances quality and memory efficiency.
On H100 NVL 188GB, embeddinggemma 300M achieves approximately 4.2 tokens per second decode speed with a time-to-first-token of 46095ms using Q6_K quantization.
For coding workloads, embeddinggemma 300M on H100 NVL 188GB receives a D grade with 4.2 tok/s and 26.8M context.
On H100 NVL 188GB, embeddinggemma 300M can safely use up to 26.8M tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/hf-ggml-org--embeddinggemma-300m-gguf-on-h100-nvl-188gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
0.2 GB |
| Medium |
| D37 |
Q4_K_M | 4 | 0.2 GB | Medium | D37 |
Q5_K_M | 5 | 0.2 GB | High | D37 |
Q6_K | 6 | 0.2 GB | High | D37 |
Q8_0 | 8 | 0.3 GB | Very High | D37 |
F16Best for your GPU | 16 | 0.6 GB | Maximum | D37 |
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.