llmrun
WaveCutYuE2ForCausalLM

YuE2 3B OrbitQuant W4A4 — Hardware Requirements & GPU Compatibility

Chat

YuE2 3B OrbitQuant W4A4 is a 2.2B-parameter open language model from WaveCut. It supports a context window of up to 24,576 tokens. At BF16 it needs about 4.98 GB of VRAM — see which GPUs and Macs can run it below.

2.2B params · dense25K contextCC BY-NC 4.03.1K downloads5 likes
S

Runs great on a 24 GB GPU

Runs from8 GB BF16 · 24KBest on24 GB BF16 · ~132 tok/s · 24KMacs from16 GB BF16 · ~28 tok/s

CC BY-NC 4.0

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run YuE2 3B OrbitQuant W4A4

One recommended way. Every other method, OS and quant is in the step-by-step guide.Each way opens a step-by-step guide for your OS and quant.

Recommended

vLLM
one command · needs vLLM installed
$vllm serve WaveCut/YuE2-3B-OrbitQuant-W4A4 --max-model-len 16384

vLLM repo with its own quantisation

Download: Weights on Hugging Face

install, OS, other quants

Ways to runOther ways

each opens step-by-step

Run in cloud

Runs on RTX 3080 Ti (12 GB) (5 GB headroom) · BF16

Generation speed
~119 tok/s
generation speed
Cost per 1M output tokens
$0.29
per 1M output tokens

How Much VRAM Does YuE2 3B OrbitQuant W4A4 Need?

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

QuantizationVRAM+32KOn RTX 4090 (reference)
5.0 GB—16-bit · bfloat — Brain floating point 16 — preferred for trainingFits: 24K context · ~132 tok/s
est.calculated, no published file yet

Selected BF16

Brain floating point 16

6.6GBat 16K context

Weights
4.5 GB
KV cache
1.9 GB
Overhead
0.3 GB

Fits RTX 4090 (reference) · 17.4 GB free · ~132 tok/s

≥50 tok/s needs ≥383 GB/s · RTX 5090 ~234, RTX 3090 Ti ~132

Which Hardware Can Run YuE2 3B OrbitQuant W4A4?

BF16 · 5.0 GB

YuE2 3B OrbitQuant W4A4 (BF16) requires 5.0 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 7+ GB is recommended. Using the full 25K context window can add up to 2.6 GB, bringing total usage to 7.6 GB. 52 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti. 151 devices with unified memory can run YuE2 3B OrbitQuant W4A4, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB).

By VRAM tier · typical GPUs and Macs at BF16
8 GB · RTX 4060BF16 · 6.6 GB · ~36 tok/s · 24K8 GB tier →
12 GB · RTX 3060 12GBBF16 · 6.6 GB · ~47 tok/s · 24K12 GB tier →
16 GB · RTX 5060 Ti 16GBBF16 · 6.6 GB · ~59 tok/s · 24K16 GB tier →
24 GB · RTX 4090referenceBF16 · 6.6 GB · ~132 tok/s · 24K24 GB tier →
Mac 32 GB · Mac Mini M4BF16 · 6.6 GB · ~17 tok/s · 24KMacs →
Mac 64 GB · Mac Studio M4 MaxBF16 · 6.6 GB · ~77 tok/s · 24KMacs →

Alternatives to YuE2 3B OrbitQuant W4A4

Similar models

6
ModelScoreVRAMtok/sWhy it is similar
LFM3 Omni 2BLiquid AI—2.4 GB~385same size
Qwen3.5 2BAlibaba—1.9 GB~370same size
Qwen3 VL 2B InstructAlibaba—3.5 GB~362same size
Qwen2 VL 2B InstructAlibaba—2.1 GB~390same size
Kimi K3 DSparkRadixArk—2.2 GB~381same size
Qwen3.8 2Bempero-ai—1.9 GB~370same size

Specifications

Publisher
WaveCut
Parameters
2.2B
Architecture
YuE2ForCausalLM
Context Length
24,576 tokens
Vocabulary Size
184,704
Release Date
2026-09-11
License
CC BY-NC 4.0

Frequently Asked Questions

How much VRAM does YuE2 3B OrbitQuant W4A4 need?

YuE2 3B OrbitQuant W4A4 requires 5.0 GB of VRAM at BF16. Full 25K context adds up to 2.6 GB (7.6 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 2.2B × 16 bits ÷ 8 = 4.4 GB

KV Cache + Overhead ≈ 0.6 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.2 GB (at full 25K context)

VRAM usage by quantization

5.0 GB
7.6 GB

Learn more about VRAM estimation →

Can I run YuE2 3B OrbitQuant W4A4 on a Mac?

Yes — Mac Mini M2 Pro (16 GB) and 133 other Macs can run YuE2 3B OrbitQuant W4A4. Apple Silicon uses unified memory, so the model shares RAM with the system. At BF16 you need at least 5.0 GB of usable unified memory (RAM minus macOS overhead).

Can I run YuE2 3B OrbitQuant W4A4 locally?

Yes — YuE2 3B OrbitQuant W4A4 can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is YuE2 3B OrbitQuant W4A4?

At BF16, YuE2 3B OrbitQuant W4A4 can reach ~964 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~132 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = (bandwidth GB/s ÷ model GB) × efficiency

Example: NVIDIA B200 → 8000 ÷ 4.98 × 0.65 = ~1044 tok/s

Estimated speed at BF16 (5.0 GB)

~1044 tok/s
~132 tok/s
~1044 tok/s
~964 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 YuE2 3B OrbitQuant W4A4?

At BF16, the download is about 4.45 GB.

Which GPUs can run YuE2 3B OrbitQuant W4A4?

52 consumer GPUs can run YuE2 3B OrbitQuant W4A4 at BF16. Top options include AMD Radeon RX 6700 XT, AMD Radeon RX 6800, AMD Radeon RX 6800 XT. 52 GPUs have plenty of headroom for comfortable inference.

Which devices can run YuE2 3B OrbitQuant W4A4?

151 devices with unified memory can run YuE2 3B OrbitQuant W4A4 at BF16 (5.0 GB), including AMD Ryzen AI 9 HX 370 (Strix Point) Laptop, ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (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.