llmrun
osunlpQwen3_5MoeForConditionalGeneration

QUEST 35B RL — Hardware Requirements & GPU Compatibility

Chat

QUEST 35B RL is a 35.1B-parameter open language model from osunlp. It supports a context window of up to 262,144 tokens. At BF16 it needs about 70.60 GB of VRAM — see which GPUs and Macs can run it below.

35.1B params · MoE3.9B active262K contextApache 2.0403 downloads4 likes

QUEST 35B RL runs on a 96 GB+ Mac or a workstation GPU

Best local pick → Mac Studio (M3 Ultra, 96GB) · BF16 · 70.7 GB · ~46 tok/s

Macs from96 GB BF16 · ~46 tok/s

Apache 2.0

Not set up for it?

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run QUEST 35B RL

One recommended way. Every other method, OS and quant is in the step-by-step guide.

Recommended

vLLM
one command · needs vLLM installed
$vllm serve osunlp/QUEST-35B-RL --max-model-len 16384 --tensor-parallel-size 8

vLLM repo with its own quantisation

Download: Weights on Hugging Face

install, OS, other quants

Other ways

each opens step-by-step

Run in cloud

Fits on RTX PRO 6000 (96 GB) (25 GB headroom) · BF16

Generation speed
~112 tok/s
generation speed
Cost per 1M output tokens
$3.05
per 1M output tokens

How Much VRAM Does QUEST 35B RL Need?

Select a quantization level; the listed hardware adheres to it.

QuantizationVRAM+32KRuns on
70.6 GB70.9 GB16-bit · bfloat — Brain floating point 16 — preferred for trainingRuns on RTX PRO 5000 Blackwell 72 GB
est.calculated, no published file yet

Selected BF16

Brain floating point 16

70.7GBat 16K context

Weights
70.2 GB
KV cache
0.2 GB
Overhead
0.3 GB

Server-class: ~70.7 GB at 16K context · one RTX PRO 5000 Blackwell 72 GB

Or rent RTX PRO 6000 from $1.23/hr.

Which Hardware Can Run QUEST 35B RL?

BF16 · 70.6 GB

QUEST 35B RL (BF16) requires 70.6 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 92+ GB is recommended. Using the full 262K context window can add up to 2.6 GB, bringing total usage to 73.2 GB. No consumer GPU has enough memory. 30 devices with unified memory can run QUEST 35B RL, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB), Mac Studio (M3 Ultra, 96GB).

By VRAM tier · typical GPUs and Macs at BF16

Consumer GPUs (up to 32 GB) and Macs up to 64 GB: too small for this model (needs ≥ 70.7 GB)8 GB tier →12 GB tier →16 GB tier →24 GB tier →Macs →

Alternatives to QUEST 35B RL

Similar models

6
ModelScoreVRAMWhy it is similar
Qwen3.6 35B A3BAlibaba106.822 GBsame size
MiniCPM V 4.7 35B A3BOpenBMB—22.1 GBsame size
Ornith 1.5 35B A3Bornith-ai—22 GBsame size
Agents A1InternScience—21.5 GBsame size
Intern S2 PreviewInternLM—73.2 GBsame size
EXAONE 4.5 33BLGAI-EXAONE—23.9 GBsame size

Specifications

Publisher
osunlp
Parameters
35.1B
Active parameters
3.9B per token
Architecture
Qwen3_5MoeForConditionalGeneration
Context Length
262,144 tokens
Vocabulary Size
248,320
Release Date
2026-05-08
License
Apache 2.0

Frequently Asked Questions

How much VRAM does QUEST 35B RL need?

QUEST 35B RL requires 70.6 GB of VRAM at BF16. Full 262K context adds up to 2.6 GB (73.2 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 35.1B × 16 bits ÷ 8 = 70.2 GB

KV Cache + Overhead ≈ 0.4 GB (at 2K context + ~0.3 GB framework)

Fit ratings and hardware model lists check this model with room for a 16K-token context, which needs a little more memory.

KV Cache + Overhead ≈ 3 GB (at full 262K context)

VRAM usage by quantization

70.6 GB
73.2 GB

Learn more about VRAM estimation →

Can NVIDIA GeForce RTX 5090 run QUEST 35B RL?

No — QUEST 35B RL requires at least 70.6 GB at BF16, which exceeds the NVIDIA GeForce RTX 5090's 32 GB of VRAM.

Can I run QUEST 35B RL on a Mac?

Yes — Mac Studio (M3 Ultra, 96GB) and 20 other Macs can run QUEST 35B RL. Apple Silicon uses unified memory, so the model shares RAM with the system. At BF16 you need at least 70.6 GB of usable unified memory (RAM minus macOS overhead).

Can I run QUEST 35B RL locally?

Yes — QUEST 35B RL can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is QUEST 35B RL?

At BF16, QUEST 35B RL can reach ~104 tok/s on AMD Instinct MI350X. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = 1000 ÷ (active GB ÷ (bandwidth GB/s × efficiency) × 1000 + layers × routing ms)

Mixture-of-Experts: just the active experts get read for each token, along with a fixed routing cost per layer.

Example: NVIDIA B200 → 7.8 GB active ÷ (8000 × 0.65) = 1.51 ms, plus 40 layers × 0.055 ms = 2.20 ms, so 1000 ÷ 3.71 ms = ~270 tok/s

Estimated speed at BF16 (70.6 GB)

~270 tok/s
~270 tok/s
~214 tok/s

Real-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.

Learn more about tok/s estimation →

What's the download size of QUEST 35B RL?

At BF16, the download is about 70.21 GB.

Which GPUs can run QUEST 35B RL?

No single consumer GPU has enough VRAM to run QUEST 35B RL at BF16 (70.6 GB). Multi-GPU or professional hardware is required.

Which devices can run QUEST 35B RL?

30 devices with unified memory can run QUEST 35B RL at BF16 (70.6 GB), including ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (Ryzen AI Max+ 395, 128 GB), GMKtec EVO-X2 (Ryzen AI Max+ 395, 128 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.