Can Granite Code 34B run on NVIDIA DGX Spark 128GB?

YES — With F16

A74Great

Estimated from fit model

Granite Code 34B needs ~87.6 GB VRAM. NVIDIA DGX Spark 128GB has 0 MB. With F16 quantization, expect ~4 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: LowStack: 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.

Granite Code 34B at Q4_K_M needs 25.6 GB — too much for NVIDIA DGX Spark 128GB (0.0 GB). Runs at F16 (87.6 GB) with maximum quality. 8 quantization levels fit.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 38.7 GB, 8.6 tok/s, Runs well

38.7 GB required108.8 GB available

36% VRAM used

Fit status

Runs well

Decode

8.6 tok/s

TTFT

22628 ms

Safe context

Memory

38.7 GB / 108.8 GB

Memory breakdown

Weights20.7 GB

KV Cache3.7 GB

Runtime1.2 GB

Headroom13.1 GB

See how fast it feels

See how fast it feelsGranite Code 34B 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: 8.6 tok/s decode · 22.6s TTFT (warm) · 21 tok/s prefill

What limits this setup

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.

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	F	Too heavy	2.0 tok/s	52800 ms	4K
Coding	F	Too heavy	2.0 tok/s	96800 ms	4K
Agentic Coding	B	Runs well	8.6 tok/s	32913 ms	8K
Reasoning	F	Too heavy	2.0 tok/s	114400 ms	4K
RAG	F	Too heavy	2.0 tok/s	176000 ms	4K

Quantization options

How Granite Code 34B (34B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	13.3 GB	Low	B67
Q3_K_S	3	16.7 GB	Low	B67
NVFP4	4	19.0 GB	Medium	B68
Q4_K_M	4	20.7 GB	Medium	B68
Q5_K_M	5	24.5 GB	High	B69
Q6_K	6	27.9 GB	High	B69
Q8_0	8	36.4 GB	Very High	A71
F16Best for your GPU	16	69.7 GB	Maximum	A75

Get started

Copy-paste commands to run Granite Code 34B on your machine.

Run

ollama run granite-code:34b

Opções de upgrade

Hardware que roda bem Granite Code 34B

NVIDIA H200 141GBOpção econômica

141 GB VRAM (+13)4800 GB/s (+4527)

Raises estimated decode speed by about 2349%.210.6 tok/s decodificação

Raises estimated decode speed by about 2349%.

Adds memory headroom for longer context windows and future model growth.

~$30,000 MSRP

NVIDIA H200 PCIe 141GBMelhor custo-benefício

141 GB VRAM (+13)4800 GB/s (+4527)

Raises estimated decode speed by about 2349%.210.6 tok/s decodificação

Raises estimated decode speed by about 2349%.

Adds memory headroom for longer context windows and future model growth.

~$30,000 MSRP

NVIDIA B200 180GBUpgrade NVIDIA

180 GB VRAM (+52)8000 GB/s (+7727)

Raises estimated decode speed by about 3981%.351 tok/s decodificação

Raises estimated decode speed by about 3981%.

Adds memory headroom for longer context windows and future model growth.

~$30,000 MSRP

Frequently asked questions

Can NVIDIA DGX Spark 128GB run Granite Code 34B?

Yes, NVIDIA DGX Spark 128GB can run Granite Code 34B at F16 quantization (Runs well). The recommended Q4_K_M requires 25.6 GB which exceeds available memory, but at F16 it needs only 87.6 GB. Expected decode speed: 3.6 tok/s.

How much VRAM does Granite Code 34B need?

Granite Code 34B (34B parameters) requires approximately 25.6 GB at Q4_K_M quantization. On NVIDIA DGX Spark 128GB, it fits at F16 using 87.6 GB.

What is the best quantization for Granite Code 34B?

The recommended quantization is Q4_K_M, but on NVIDIA DGX Spark 128GB the best fitting quantization is F16, which uses 87.6 GB.

What speed will Granite Code 34B run at on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, Granite Code 34B achieves approximately 3.6 tokens per second decode speed with a time-to-first-token of 54317ms using F16 quantization.

Can NVIDIA DGX Spark 128GB run Granite Code 34B for coding?

For coding workloads, Granite Code 34B on NVIDIA DGX Spark 128GB receives a F grade with 2.0 tok/s and 4K context.

What context window can Granite Code 34B use on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, Granite Code 34B 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.

What should I upgrade first if Granite Code 34B feels slow on NVIDIA DGX Spark 128GB?

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.

Is unified memory on NVIDIA DGX Spark 128GB as fast as VRAM for Granite Code 34B?

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.

See all results for NVIDIA DGX Spark 128GB See all hardware for Granite Code 34B

Embed this result▼

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/granite-code-34b-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: