Can Aya Expanse 32B run on Gaudi 3 128GB?

YES — Runs Great

C53Usable

○Estimated from fit model

Aya Expanse 32B needs ~35.7 GB VRAM. Gaudi 3 128GB has 128.0 GB. With Q4_K_M quantization, expect ~144 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) — 35.7 GB, 144.3 tok/s, Runs well

35.7 GB required128.0 GB available

28% VRAM used

Fit status

Runs well

Decode

144.3 tok/s

TTFT

1342 ms

Safe context

Memory

35.7 GB / 128.0 GB

Memory breakdown

Weights19.5 GB

KV Cache2.4 GB

Runtime0.9 GB

Headroom12.8 GB

See how fast it feels

See how fast it feelsAya Expanse 32B on Gaudi 3 128GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API.

When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed.

Key benefits of running locally:
 - Full privacy: your prompts never leave your machine
 - No per-token cost or rate limits
 - Works offline once the model is downloaded
 - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb:

 Model size Q4 (4-bit) Q8 (8-bit) FP16
 7B params ~4.3 GB ~7.5 GB ~14 GB
 13B params ~7.9 GB ~13.9 GB ~26 GB
 70B params ~42.7 GB ~74.9 GB ~140 GB

Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 144.3 tok/s decode · 1.3s TTFT (warm) · 361 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	144.3 tok/s	732 ms	8K
Coding	C	Runs well	144.3 tok/s	1342 ms	8K
Agentic Coding	C	Runs well	144.3 tok/s	1952 ms	8K
Reasoning	C	Runs well	144.3 tok/s	1586 ms	8K
RAG	C	Runs well	144.3 tok/s	2439 ms	8K

Quantization options

How Aya Expanse 32B (32B params) fits at each quantization level on Gaudi 3 128GB (128.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	12.5 GB	Low	C44
Q3_K_S	3	15.7 GB	Low	C44
NVFP4	4	17.9 GB	Medium	C44
Q4_K_M	4	19.5 GB	Medium	C44
Q5_K_M	5	23.0 GB	High	C45
Q6_K	6	26.2 GB	High	C45
Q8_0	8	34.2 GB	Very High	C47
F16Best for your GPU	16	65.6 GB	Maximum	C52

Get started

Copy-paste commands to run Aya Expanse 32B on your machine.

Run

ollama run aya-expanse:32b

Frequently asked questions

See all results for Gaudi 3 128GB See all hardware for Aya Expanse 32B

URL: https://willitrunai.com/can-run/aya-expanse-32b-on-gaudi-3-128gb