mxbai Embed Large needs ~16.4 GB VRAM. NVIDIA DGX Spark 128GB has 0 MB. With F16 quantization, expect ~5 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.7 tok/s
TTFT
41279 ms
Safe context
512
Memory
16.4 GB / 108.8 GB
The model fits in shared memory, but shared-memory bandwidth is now the real limiter.
Fit does not mean dedicated-VRAM speed
Unified or shared memory can make a model technically fit, but sustained tokens per second may still trail a discrete high-bandwidth GPU with less total memory.
Shared-memory contention still exists
The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.
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 | B | Runs well | 4.7 tok/s | 22516 ms | 512 |
| Coding | F | Too heavy | 4.7 tok/s | 41279 ms | 512 |
| Agentic Coding | A | Runs well | 4.7 tok/s | 60043 ms | 512 |
| Reasoning | A | Runs well | 4.7 tok/s | 48785 ms | 512 |
| RAG | A | Runs well | 4.7 tok/s | 75053 ms | 512 |
How mxbai Embed Large (0.33500000834465027B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 0.1 GB | Low | A73 |
Q3_K_S | 3 | 0.2 GB | Low | A73 |
NVFP4 | 4 |
Copy-paste commands to run mxbai Embed Large on your machine.
Run
ollama run mxbai-embed-largeUpgrade options
Yes, NVIDIA DGX Spark 128GB can run mxbai Embed Large at F16 quantization (Runs well). The recommended F16 requires 2.9 GB which exceeds available memory, but at F16 it needs only 16.4 GB. Expected decode speed: 4.7 tok/s.
mxbai Embed Large (0.33500000834465027B parameters) requires approximately 2.9 GB at F16 quantization. On NVIDIA DGX Spark 128GB, it fits at F16 using 16.4 GB.
The recommended quantization is F16, but on NVIDIA DGX Spark 128GB the best fitting quantization is F16, which uses 16.4 GB.
On NVIDIA DGX Spark 128GB, mxbai Embed Large achieves approximately 4.7 tokens per second decode speed with a time-to-first-token of 41279ms using F16 quantization.
For coding workloads, mxbai Embed Large on NVIDIA DGX Spark 128GB receives a F grade with 4.7 tok/s and 512 context.
On NVIDIA DGX Spark 128GB, mxbai Embed Large can safely use up to 512 tokens of context at F16 quantization. The model's official context limit is 512, 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/mxbai-embed-large-on-dgx-spark-128gb" 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 |
| A73 |
Q4_K_M | 4 | 0.2 GB | Medium | A73 |
Q5_K_M | 5 | 0.2 GB | High | A73 |
Q6_K | 6 | 0.3 GB | High | A73 |
Q8_0 | 8 | 0.4 GB | Very High | A73 |
F16Best for your GPU | 16 | 0.7 GB | Maximum | A73 |
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.
Not always. NVIDIA DGX Spark 128GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.