Would CUDA be a better path than Intel Arc A770 16GB for Qwen3.5 35B A3B?

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 Qwen3.5 35B A3B run on Intel Arc A770 16GB?

Q: What should I upgrade first if Qwen3.5 35B A3B feels slow on Intel Arc A770 16GB?

Add more VRAM headroom. The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.

NO — Won't Fit

F0Won't run

Estimated from fit model

Qwen3.5 35B A3B needs ~28.0 GB but Intel Arc A770 16GB only has 16.0 GB. Try a smaller quantization or lighter model.

Runtime: llama.cppCapacity: No fitBandwidth: MediumStack: StandardBottleneck: Memory capacity

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) — 28.0 GB, exceeds 16.0 GB available

28.0 GB required16.0 GB available

175% VRAM needed

12.0 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

2.7 tok/s

TTFT

70771 ms

Safe context

Memory

28.0 GB / 16.0 GB

Offload

40%

Memory breakdown

Weights21.3 GB

KV Cache4.1 GB

Runtime0.9 GB

Headroom1.6 GB

See how fast it feels

With memory offload — actual speed may be lower

See how fast it feelsQwen3.5 35B A3B on Intel Arc A770 16GB
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: 2.7 tok/s decode · 70.8s TTFT (warm) · 7 tok/s prefill

What limits this setup

Usable VRAM is the main blocker for this model.

Not enough usable memory

The model needs 28.0 GB, but this setup only exposes 16.0 GB of usable VRAM.

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

Add more VRAM headroom

The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.

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	F	Too heavy	3.2 tok/s	32881 ms	4K
Coding	F	Too heavy	2.7 tok/s	70771 ms	4K
Agentic Coding	F	Too heavy	2.1 tok/s	137326 ms	4K
Reasoning	F	Too heavy	2.7 tok/s	83638 ms	4K
RAG	F	Too heavy	2.1 tok/s	171658 ms	4K

Quantization options

How Qwen3.5 35B A3B (35B params) fits at each quantization level on Intel Arc A770 16GB (16.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	13.7 GB	Low	F0
Q3_K_S	3	17.2 GB	Low	F0
NVFP4	4

Upgrade options

Hardware that runs Qwen3.5 35B A3B well

Intel Arc Pro B60 24GBBest value

24 GB VRAM (+8)

Makes the model fit on the accelerator instead of staying completely out of reach.6.1 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Raises estimated decode speed by about 126%.

~$599 MSRP

NVIDIA A100 40GBBiggest leap

40 GB VRAM (+24)1555 GB/s (+995)

Makes the model fit on the accelerator instead of staying completely out of reach.61.2 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$10,000 MSRP

Intel Data Center GPU Max 1550 128GBBudget pick

128 GB VRAM (+112)3200 GB/s (+2640)

Makes the model fit on the accelerator instead of staying completely out of reach.94.4 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$15,000 MSRP

Gaudi 3 128GBIntel upgrade

128 GB VRAM (+112)3700 GB/s (+3140)

Makes the model fit on the accelerator instead of staying completely out of reach.121.3 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$15,000 MSRP

Frequently asked questions

Can Intel Arc A770 16GB run Qwen3.5 35B A3B?

No, Qwen3.5 35B A3B requires more memory than Intel Arc A770 16GB provides.

How much VRAM does Qwen3.5 35B A3B need?

Qwen3.5 35B A3B (35B parameters) requires approximately 28.0 GB of memory with Q4_K_M quantization.

What is the best quantization for Qwen3.5 35B A3B?

The recommended quantization for Qwen3.5 35B A3B is Q4_K_M, which balances quality and memory efficiency.

What speed will Qwen3.5 35B A3B run at on Intel Arc A770 16GB?

On Intel Arc A770 16GB, Qwen3.5 35B A3B achieves approximately 2.7 tokens per second decode speed with a time-to-first-token of 70771ms using Q4_K_M quantization.

Can Intel Arc A770 16GB run Qwen3.5 35B A3B for coding?

For coding workloads, Qwen3.5 35B A3B on Intel Arc A770 16GB receives a F grade with 2.7 tok/s and 4K context.

What context window can Qwen3.5 35B A3B use on Intel Arc A770 16GB?

On Intel Arc A770 16GB, Qwen3.5 35B A3B can safely use up to 4K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.

What should I upgrade first if Qwen3.5 35B A3B feels slow on Intel Arc A770 16GB?

See all results for Intel Arc A770 16GB See all hardware for Qwen3.5 35B A3B

Embed this result▼

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

<iframe src="https://willitrunai.com/embed/hf-lmstudio-community--qwen3-5-35b-a3b-gguf-on-arc-a770-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: