Mac Studio M3 Ultra 256GBコスパ重視
256 GB Unified (+128)819 GB/s (+546)
B
Adds memory headroom for longer context windows and future model growth.42 tok/sデコード
Adds memory headroom for longer context windows and future model growth.
〜$6,999 MSRP
Can Granite Code 3B run on NVIDIA DGX Spark 128GB?
YES — With F16
B60Good
Estimated from fit model
Granite Code 3B needs ~22.9 GB VRAM. NVIDIA DGX Spark 128GB has 0 MB. With F16 quantization, expect ~37 tok/s.
Runtime: OllamaCapacity: RoomyBandwidth: LowStack: BasicBottleneck: 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.
Granite Code 3B at Q4_K_M needs 5.5 GB — too much for NVIDIA DGX Spark 128GB (0.0 GB). Runs at F16 (22.9 GB) with maximum quality. 8 quantization levels fit.
Select quantization to explore
Q4_K_M (Medium quality) — 18.6 GB, 42.0 tok/s, Runs well
18.6 GB required108.8 GB available
17% VRAM used
Fit status
Runs well
Decode
42.0 tok/s
TTFT
4610 ms
Safe context
8K
Memory
18.6 GB / 108.8 GB
Memory breakdown
Weights1.8 GB
KV Cache2.5 GB
Runtime1.2 GB
Headroom13.1 GB
See how fast it feels
See how fast it feelsGranite Code 3B on NVIDIA DGX Spark 128GB
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: 42.0 tok/s decode · 4.6s TTFT (warm) · 105 tok/s prefill
What limits this setup
This setup is broadly balanced for this model.
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.
Best improvement path
Performance by workload
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | F | Too heavy | 16.1 tok/s | 6554 ms | 4K |
| Coding | F | Too heavy | 16.1 tok/s | 12016 ms | 4K |
| Agentic Coding | F | Too heavy | 16.1 tok/s | 17478 ms | 4K |
| Reasoning | F | Too heavy | 16.1 tok/s | 14201 ms | 4K |
| RAG | F | Too heavy | 16.1 tok/s | 21848 ms | 4K |
Quantization options
How Granite Code 3B (3B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 1.2 GB | Low | B55 |
Q3_K_S | 3 | 1.5 GB | Low | B55 |
NVFP4 | 4 | 1.7 GB | Medium | B55 |
Q4_K_M | 4 | 1.8 GB | Medium | B55 |
Q5_K_M | 5 | 2.2 GB | High | B55 |
Q6_K | 6 | 2.5 GB | High | B55 |
Q8_0 | 8 | 3.2 GB | Very High | B55 |
F16Best for your GPU | 16 | 6.1 GB | Maximum | B55 |
Get started
Copy-paste commands to run Granite Code 3B on your machine.
Run
ollama run granite-code:3bアップグレードオプション
Granite Code 3Bを快適に動かすハードウェア
Frequently asked questions
Can NVIDIA DGX Spark 128GB run Granite Code 3B?
Yes, NVIDIA DGX Spark 128GB can run Granite Code 3B at F16 quantization (Runs well). The recommended Q4_K_M requires 5.5 GB which exceeds available memory, but at F16 it needs only 22.9 GB. Expected decode speed: 37.3 tok/s.
How much VRAM does Granite Code 3B need?
Granite Code 3B (3B parameters) requires approximately 5.5 GB at Q4_K_M quantization. On NVIDIA DGX Spark 128GB, it fits at F16 using 22.9 GB.
What is the best quantization for Granite Code 3B?
The recommended quantization is Q4_K_M, but on NVIDIA DGX Spark 128GB the best fitting quantization is F16, which uses 22.9 GB.
What speed will Granite Code 3B run at on NVIDIA DGX Spark 128GB?
On NVIDIA DGX Spark 128GB, Granite Code 3B achieves approximately 37.3 tokens per second decode speed with a time-to-first-token of 5192ms using F16 quantization.
Can NVIDIA DGX Spark 128GB run Granite Code 3B for coding?
For coding workloads, Granite Code 3B on NVIDIA DGX Spark 128GB receives a F grade with 16.1 tok/s and 4K context.
What context window can Granite Code 3B use on NVIDIA DGX Spark 128GB?
On NVIDIA DGX Spark 128GB, Granite Code 3B can safely use up to 8K tokens of context at F16 quantization. The model's official context limit is 8K, but available memory constrains the safe maximum.
Is unified memory on NVIDIA DGX Spark 128GB as fast as VRAM for Granite Code 3B?
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.
Embed this result▼
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/granite-code-3b-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: