Can Qwen 3.5 35B A3B run on RTX A5500 24GB?

BARELY — Tight on Memory

A84Great

Estimated from fit model

Qwen 3.5 35B A3B needs ~26.1 GB VRAM. RTX A5500 24GB has 24.0 GB. With Q4_K_M quantization, expect ~52 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: MediumStack: StandardBottleneck: Host offload

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) — 26.1 GB, 52.0 tok/s, Very compromised (needs ~1.7 GB host RAM)

26.1 GB required24.0 GB available

109% VRAM needed

2.1 GB over capacity — needs offload or smaller quantization

Fit status

Very compromised (needs ~1.7 GB host RAM)

Decode

52.0 tok/s

TTFT

3725 ms

Safe context

Memory

26.1 GB / 24.0 GB

Offload

10%

Memory breakdown

Weights21.3 GB

KV Cache1.5 GB

Runtime0.9 GB

Headroom2.4 GB

See how fast it feels

See how fast it feelsQwen 3.5 35B A3B on RTX A5500 24GB
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: 52.0 tok/s decode · 3.7s TTFT (warm) · 130 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.

Very little memory headroom

You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.

Best improvement path

Remove offload with more accelerator memory

Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Buy headroom, not only minimum fit

A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.

Increase host RAM if you keep offloading

This setup may need roughly 1.7 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	A	Runs with offload (needs ~1.2 GB host RAM)	55.2 tok/s	1914 ms	4K
Coding	A	Very compromised (needs ~1.7 GB host RAM)	52.0 tok/s	3725 ms	4K
Agentic Coding	A	Very compromised (needs ~2.8 GB host RAM)	46.3 tok/s	6077 ms	4K
Reasoning	A	Very compromised (needs ~1.7 GB host RAM)	52.0 tok/s	4402 ms	4K
RAG	A	Very compromised (needs ~2.8 GB host RAM)	46.3 tok/s	7596 ms	4K

Inference speed

Qwen 3.5 35B A3B inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for Qwen 3.5 35B A3B at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~139 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.

GPU / Mac	Memory	Quant	Speed (tok/s)	Fits?
RTX 5090 32GB	32 GB	Q4_K_M	139.4	Tight
Mac Studio M3 Ultra 256GB	256 GB	Q4_K_M	100.1	Fits
Mac Studio M2 Ultra 128GB	128 GB	Q4_K_M	83.4	Fits
Mac Studio M1 Ultra 128GB	128 GB	Q4_K_M	79.1	Fits
RTX 4090 24GB	24 GB	Q4_K_M	71.1	Heavy offload
MacBook Pro M4 Max 128GB	128 GB	Q4_K_M	61.8	Fits
MacBook Pro M4 Max 64GB	64 GB	Q4_K_M	61.8	Fits
RX 7900 XTX 24GB	24 GB	Q4_K_M	60.0	Heavy offload
RTX 3090 24GB	24 GB	Q4_K_M	56.9	Heavy offload
MacBook Pro M3 Max 64GB	64 GB	Q4_K_M	47.4	Fits
MacBook Pro M1 Max 64GB	64 GB	Q4_K_M	43.5	Fits
MacBook Pro M4 Pro 48GB	48 GB	Q4_K_M	41.5	Tight
RTX 4080 Super 16GB	16 GB	Q4_K_M	25.2	Too big
RTX 4070 12GB	12 GB	Q4_K_M	8.8	Too big
RTX 3060 12GB	12 GB	Q4_K_M	5.2	Too big
RTX 4060 8GB	8 GB	Q4_K_M	4.4	Too big

Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.

Quantization options

How Qwen 3.5 35B A3B (35B params) fits at each quantization level on RTX A5500 24GB (24.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	13.7 GB	Low	S92
Q3_K_SBest for your GPU	3	17.2 GB	Low	S91
NVFP4	4	19.6 GB	Medium	F0
Q4_K_M	4	21.3 GB	Medium	F0
Q5_K_M	5	25.2 GB	High	F0
Q6_K	6	28.7 GB	High	F0
Q8_0	8	37.5 GB	Very High	F0
F16	16	71.8 GB	Maximum	F0

Get started

Copy-paste commands to run Qwen 3.5 35B A3B on your machine.

Run

ollama run qwen3.5:35b-a3b

Frequently asked questions

Can RTX A5500 24GB run Qwen 3.5 35B A3B?

Yes, RTX A5500 24GB can run Qwen 3.5 35B A3B with a A grade (Very compromised (needs ~1.7 GB host RAM)). Expected decode speed: 52.0 tok/s.

How much VRAM does Qwen 3.5 35B A3B need?

Qwen 3.5 35B A3B (35B parameters) requires approximately 26.1 GB of memory with Q4_K_M quantization.

What is the best quantization for Qwen 3.5 35B A3B?

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

What speed will Qwen 3.5 35B A3B run at on RTX A5500 24GB?

On RTX A5500 24GB, Qwen 3.5 35B A3B achieves approximately 52.0 tokens per second decode speed with a time-to-first-token of 3725ms using Q4_K_M quantization.

Can RTX A5500 24GB run Qwen 3.5 35B A3B for coding?

For coding workloads, Qwen 3.5 35B A3B on RTX A5500 24GB receives a A grade with 52.0 tok/s and 4K context.

What context window can Qwen 3.5 35B A3B use on RTX A5500 24GB?

On RTX A5500 24GB, Qwen 3.5 35B A3B can safely use up to 4K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.

What should I upgrade first if Qwen 3.5 35B A3B feels slow on RTX A5500 24GB?

Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

See all results for RTX A5500 24GB See all hardware for Qwen 3.5 35B A3B

Embed this result▼

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

<iframe src="https://willitrunai.com/embed/qwen-3.5-35b-a3b-on-rtx-a5500-24gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: