Would CUDA be a better path than Gaudi 3 128GB for StarCoder2 15B?

Often yes, if your goal is the easiest setup and the widest runtime support. Intel can offer attractive memory capacity, but CUDA still tends to win on tooling maturity, guides, kernels, and model coverage for local AI.

Can StarCoder2 15B run on Gaudi 3 128GB?

Q: What should I upgrade first if StarCoder2 15B feels slow on Gaudi 3 128GB?

Prefer CUDA if you want the path of least resistance. If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.

YES — Runs Great

C46Usable

Estimated from fit model

StarCoder2 15B needs ~24.6 GB VRAM. Gaudi 3 128GB has 128.0 GB. With Q4_K_M quantization, expect ~210 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: HighStack: StandardBottleneck: 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.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 24.6 GB, 210.0 tok/s, Runs well

24.6 GB required128.0 GB available

19% VRAM used

Fit status

Runs well

Decode

210.0 tok/s

TTFT

922 ms

Safe context

957K

Memory

24.6 GB / 128.0 GB

Memory breakdown

Weights9.2 GB

KV Cache1.8 GB

Runtime0.9 GB

Headroom12.8 GB

See how fast it feels

See how fast it feelsStarCoder2 15B on Gaudi 3 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: 210.0 tok/s decode · 922ms TTFT (warm) · 525 tok/s prefill

What limits this setup

The raw memory story may look fine, but the software ecosystem is still a constraint here.

Runtime ecosystem is narrower than CUDA

Intel GPUs can look attractive on memory per dollar, but local AI tooling, kernels, and model coverage are still broader and easier on CUDA today.

Best improvement path

Prefer CUDA if you want the path of least resistance

If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	C	Runs well	210.0 tok/s	503 ms	957K
Coding	C	Runs well	210.0 tok/s	922 ms	957K
Agentic Coding	C	Runs well	210.0 tok/s	1341 ms	957K
Reasoning	C	Runs well	210.0 tok/s	1090 ms	957K
RAG	C	Runs well	210.0 tok/s	1676 ms	957K

Quantization options

How StarCoder2 15B (15B params) fits at each quantization level on Gaudi 3 128GB (128.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	5.9 GB	Low	D38
Q3_K_S	3	7.4 GB	Low	D38
NVFP4	4

Get started

Copy-paste commands to run StarCoder2 15B on your machine.

Run

lms load hf-second-state--starcoder2-15b-gguf && lms server start

Frequently asked questions

Can Gaudi 3 128GB run StarCoder2 15B?

Yes, Gaudi 3 128GB can run StarCoder2 15B with a C grade (Runs well). Expected decode speed: 210.0 tok/s.

How much VRAM does StarCoder2 15B need?

StarCoder2 15B (15B parameters) requires approximately 24.6 GB of memory with Q4_K_M quantization.

What is the best quantization for StarCoder2 15B?

The recommended quantization for StarCoder2 15B is Q4_K_M, which balances quality and memory efficiency.

What speed will StarCoder2 15B run at on Gaudi 3 128GB?

On Gaudi 3 128GB, StarCoder2 15B achieves approximately 210.0 tokens per second decode speed with a time-to-first-token of 922ms using Q4_K_M quantization.

Can Gaudi 3 128GB run StarCoder2 15B for coding?

For coding workloads, StarCoder2 15B on Gaudi 3 128GB receives a C grade with 210.0 tok/s and 957K context.

What context window can StarCoder2 15B use on Gaudi 3 128GB?

On Gaudi 3 128GB, StarCoder2 15B can safely use up to 957K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.

What should I upgrade first if StarCoder2 15B feels slow on Gaudi 3 128GB?

See all results for Gaudi 3 128GB See all hardware for StarCoder2 15B

Embed this result▼

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

<iframe src="https://willitrunai.com/embed/hf-second-state--starcoder2-15b-gguf-on-gaudi-3-128gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: