local desktop · Qwen 3.8 Flash

Flash with RAM offload

Qwen 3.8 Flash does not fit in one 32 GB card. Hot experts stay in VRAM. The rest lands on DDR5. Decode cells come from verified amdai-bench/run@1 Flash cards. Empty stays not measured on the local desktop. RAM kits are calculator estimates (file size + KV), labeled as such. MoE vs dense, and why 35B-A3B is a different fit, live on /moe.

Estimate · file size + KV

System RAM at 262K

Minimum system RAM is the 4K load. RAM at full context is 262144 tokens. Spill is weights plus KV that missed the VRAM pool (32 GB on one R9700, 64 GB on two). Every GiB column is an estimate. Linux GiB labeled GB.

Two R9700s · 64 GB VRAM

Quant File Spill to DDR5 Min RAM kit RAM at 262K
UD-Q3_K_XL 83.8 GB 27.4 GB est. 48 GB 64 GB
UD-Q4_K_XL 103.7 GB 47.0 GB est. 96 GB 96 GB
UD-Q5_K_XL 147.4 GB 91.0 GB est. 128 GB 128 GB
UD-Q6_K_XL 157.5 GB 101.0 GB est. 128 GB 192 GB

One R9700 · 32 GB VRAM

More of the file lands on DDR5. Decode at this card count is not measured on the local desktop.

Quant File Spill to DDR5 Min RAM kit RAM at 262K
UD-Q3_K_XL 83.8 GB 59.4 GB est. 96 GB 96 GB
UD-Q4_K_XL 103.7 GB 79.0 GB est. 128 GB 128 GB
UD-Q5_K_XL 147.4 GB 123.0 GB est. 192 GB 192 GB
UD-Q6_K_XL 157.5 GB 133.0 GB est. 192 GB 192 GB

UD-Q3_K_XL · two cards · estimate

Minimum system RAM needed

48 GB kit

Estimate · 46.4 GiB raw · 4K context

RAM needed at full context

64 GB kit

Estimate · 54.0 GiB raw · 256K full context

Estimate. Offloaded weights + KV in RAM + runtime + OS/desktop + headroom, rounded up to a 48 GB DIMM kit.

Breakdown
Offloaded weights ·
19.8 GiB
Separable embed in RAM ·
0 GiB
KV in RAM at selected ·
0.23 GiB
KV in RAM at full context ·
7.61 GiB
Runtime / backend ·
2.38 GiB
OS / desktop baseline ·
8.00 GiB
Headroom ·
16.0 GiB

UD-Q4_K_XL · two cards · estimate

Minimum system RAM needed

96 GB kit

Estimate · 66.4 GiB raw · 4K context

RAM needed at full context

96 GB kit

Estimate · 73.9 GiB raw · 256K full context

Estimate. Offloaded weights + KV in RAM + runtime + OS/desktop + headroom, rounded up to a 96 GB DIMM kit.

Breakdown
Offloaded weights ·
39.4 GiB
Separable embed in RAM ·
0 GiB
KV in RAM at selected ·
0.23 GiB
KV in RAM at full context ·
7.61 GiB
Runtime / backend ·
2.77 GiB
OS / desktop baseline ·
8.00 GiB
Headroom ·
16.0 GiB

UD-Q5_K_XL · two cards · estimate

Minimum system RAM needed

128 GB kit

Estimate · 111.3 GiB raw · 4K context

RAM needed at full context

128 GB kit

Estimate · 118.8 GiB raw · 256K full context

Estimate. Offloaded weights + KV in RAM + runtime + OS/desktop + headroom, rounded up to a 128 GB DIMM kit.

Breakdown
Offloaded weights ·
83.4 GiB
Separable embed in RAM ·
0 GiB
KV in RAM at selected ·
0.23 GiB
KV in RAM at full context ·
7.61 GiB
Runtime / backend ·
3.65 GiB
OS / desktop baseline ·
8.00 GiB
Headroom ·
16.0 GiB

UD-Q6_K_XL · two cards · estimate

Minimum system RAM needed

128 GB kit

Estimate · 121.5 GiB raw · 4K context

RAM needed at full context

192 GB kit

Estimate · 129.0 GiB raw · 256K full context

Estimate. Offloaded weights + KV in RAM + runtime + OS/desktop + headroom, rounded up to a 128 GB DIMM kit.

Breakdown
Offloaded weights ·
93.4 GiB
Separable embed in RAM ·
0 GiB
KV in RAM at selected ·
0.23 GiB
KV in RAM at full context ·
7.61 GiB
Runtime / backend ·
3.85 GiB
OS / desktop baseline ·
8.00 GiB
Headroom ·
16.0 GiB

Estimate · 96 / 128 / 192 / 256

Recommended setup per RAM kit

Picks follow the calculator kit rounding. They are not a tok/s promise. 96 GB (2x48) is the pick for most builds. 256 GB is what local desktop ships (~249 GB usable).

96 GB kit

96 GB (2x48) is the pick for most builds. Two-card Q4 at 262K fits on the calculator estimate.

  • At 262K this kit covers: UD-Q3_K_XL · 1×R9700; UD-Q3_K_XL · 2×R9700; UD-Q4_K_XL · 2×R9700 (estimate).
  • Too small for: UD-Q4_K_XL · 1×; UD-Q5_K_XL · 1×; UD-Q5_K_XL · 2×; UD-Q6_K_XL · 1×; UD-Q6_K_XL · 2× (estimate).

128 GB kit

128 GB covers two-card Q5 at 262K. Q6 only with about 4 GB spare — we size Q6 at 192 GB.

  • At 262K this kit covers: UD-Q3_K_XL · 1×R9700; UD-Q3_K_XL · 2×R9700; UD-Q4_K_XL · 1×R9700; UD-Q4_K_XL · 2×R9700; UD-Q5_K_XL · 2×R9700 (estimate).
  • Short context only: UD-Q6_K_XL · 2× (estimate).
  • Too small for: UD-Q5_K_XL · 1×; UD-Q6_K_XL · 1× (estimate).

192 GB kit

192 GB covers one-card Q6 at 262K on the calculator estimate. Speeds for that card count are not measured.

  • At 262K this kit covers: UD-Q3_K_XL · 1×R9700; UD-Q3_K_XL · 2×R9700; UD-Q4_K_XL · 1×R9700; UD-Q4_K_XL · 2×R9700; UD-Q5_K_XL · 1×R9700; UD-Q5_K_XL · 2×R9700; UD-Q6_K_XL · 1×R9700; UD-Q6_K_XL · 2×R9700 (estimate).

256 GB kit

256 GB is the local desktop kit. Two-card Q6 at 262K is the measured house fast-agent.

  • At 262K this kit covers: UD-Q3_K_XL · 1×R9700; UD-Q3_K_XL · 2×R9700; UD-Q4_K_XL · 1×R9700; UD-Q4_K_XL · 2×R9700; UD-Q5_K_XL · 1×R9700; UD-Q5_K_XL · 2×R9700; UD-Q6_K_XL · 1×R9700; UD-Q6_K_XL · 2×R9700 (estimate).

RAM sizes are estimates · speeds measured on our rig

Is more RAM worth it?

For most people, no. 96 GB (2x48 DDR5) is the right size for most builds: with two R9700s it runs Qwen 3.8 Flash Q4 at full 256K context (estimate: about 67 GB needed). Spending more on RAM lets you load a larger, smarter model, but more of that model has to sit in system RAM instead of on the graphics cards, so it answers a lot slower. It is usually not worth it unless you really want the maximum intelligence you can run at home and are okay with it being slow.

RAM kit Largest model it fits (two R9700s, 256K) RAM needed (estimate) What you get
96 GB Qwen 3.8 Flash UD-Q4_K_XL ~67 GB est. Recommended for most builds. Runs Flash Q4 at full 256K context with room to spare.
128 GB Qwen 3.8 Flash UD-Q5_K_XL / UD-Q6_K_XL ~111–121 GB est. Same model, higher-precision file. A bit smarter, and more of it sits in system RAM.
192 GB GLM-5.3-Flash UD-Q4_K_XL ~147 GB est. A larger model. Smarter on hard problems, and much more of it sits in system RAM.
256 GB GLM-5.3-Flash UD-Q5_K_XL / UD-Q6_K_XL ~184–232 GB est. The largest files we size. Maximum intelligence on this hardware, and the slowest output.

Why it gets slower: every token reads the model weights. The R9700’s own memory is 640 GB/s (AMD spec). Dual-channel DDR5 on a Ryzen 9000 desktop reads at roughly 55–64 GB/s, so weights that live in system RAM are read about 10x or more slower (spec-sheet estimate, not a benchmark). The bigger the file, the more of it lands in system RAM.

Measured on our rig: Qwen3.6-35B-A3B UD-Q5_K_XL on one R9700, fully in VRAM (llama.cpp, 4K) decodes about 102 tok/s (102.39). Qwen 3.8 Flash UD-Q6_K_XL on two R9700s with experts in DDR5-5200 (Strata, 8K) decodes about 33 tok/s (32.8) — roughly a third of the speed for a bigger, smarter model. We have not measured GLM-5.3-Flash; expect it to be slower still. Run cards: 35B one card, Flash Q6 offloaded.

Only ever running the 35B on one card? 32 GB (2x16) is enough for that, because the model stays in VRAM. Skip it if you might want Qwen 3.8 Flash later — a 2x16 kit cannot be topped up.

RAM needs are estimates for two R9700s at 262144 context with f16 KV (file size from Hugging Face, expert split from the GGUF headers, 10 GB for the OS). Not measured host RAM. The calculator adds 16 GB headroom, so it can round one size higher.

From data/runs · Flash only

Decode by quant, cards, and engine

Q3–Q6 × 1 vs 2 R9700s × llama.cpp vs Strata × 4K / 32K / 128K / 256K. A cell fills when a verified Flash run card matches. Until then it stays empty.

Quant GPUs Backend 4K32K128K256K
UD-Q3_K_XL 1 llama.cpp not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q3_K_XL 1 Strata not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q3_K_XL 2 llama.cpp not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q3_K_XL 2 Strata not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q4_K_XL 1 llama.cpp not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q4_K_XL 1 Strata not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q4_K_XL 2 llama.cpp not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q4_K_XL 2 Strata not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q5_K_XL 1 llama.cpp not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q5_K_XL 1 Strata not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q5_K_XL 2 llama.cpp not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q5_K_XL 2 Strata not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q6_K_XL 1 llama.cpp not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q6_K_XL 1 Strata not measured on the local desktop not measured on the local desktop not measured on the local desktop not measured on the local desktop
UD-Q6_K_XL 2 llama.cpp not measured on the local desktop 18.2 tok/s @5200 · 15.6 tok/s @3600 not measured on the local desktop 16 tok/s @5200
UD-Q6_K_XL 2 Strata not measured on the local desktop 32.8 tok/s @5200 not measured on the local desktop 32.6 tok/s @5200
  • No Flash Q3 decode in data/runs yet. When the approved measured card lands, this grid will show it.
  • Flash Q4 decode is not measured on the local desktop.
  • Flash Q5 decode is not measured on the local desktop.
  • One-card Flash decode cells are empty. Prior 32.6 / 16 points recorded card count as unpublished.
  • 4K Flash decode is not in the jsonl yet.
  • 128K Flash decode is not in the jsonl yet.

Measured · DDR5-3600 vs 5200

Memory speed vs decode

Same two-card Q6, same 262K load. Only the DIMM clock changes. llama.cpp at 8K is the 15.9 → 18.5 pair. Strata at 8K is the 32.0 → 32.8 pair. Missing contexts stay not measured on the local desktop.

Engine Context DDR5-3600 DDR5-5200
llama.cpp 8K 15.9 tok/s 18.5 tok/s
llama.cpp 32K 15.6 tok/s 18.2 tok/s
llama.cpp 100K 15.3 tok/s 17.9 tok/s
Strata 8K 32.0 tok/s 32.8 tok/s
Strata 32K not measured on the local desktop 32.8 tok/s
Strata 100K not measured on the local desktop 31.8 tok/s

Shape · flags not recorded

Expert-offload launch

llama.cpp places leftover experts with -ot (tensor override) and --n-cpu-moe. Strata’s equivalent is the expert-cache / RAM / SSD tier. Exact regex, N, and Strata flags are not recorded — we will not invent them.

llama.cpp Vulkan

# Shape only — exact -ot tensor regex and --n-cpu-moe N are not recorded from the rig owner.
# After --list-devices, exclude the iGPU if two Vulkan devices appear.
./build-vk/bin/llama-server \
  -m ~/models/UD-Q6_K_XL \
  -ngl 99 \
  -c 262144 \
  --n-cpu-moe not recorded \
  -ot not recorded \
  --cache-type-k f16 \
  --cache-type-v f16 \
  --host 127.0.0.1 --port 8080

Strata

# Shape only — exact expert-cache / RAM / SSD-tier flags not recorded. No MTP.
# After rocminfo, exclude the iGPU if a second HIP device appears.
# This site’s convention: 127.0.0.1:8083 so llama-server can keep :8080.
curl -s http://127.0.0.1:8083/v1/models

Do this first

Pitfalls

Exclude the iGPU

A 7900-class APU or desktop iGPU will show up next to the R9700. llama.cpp Vulkan: run --list-devices, then set GGML_VK_VISIBLE_DEVICES (and VK_ICD_FILENAMES if needed) so the process binds the discrete card. HIP / Strata: HIP_VISIBLE_DEVICES after rocminfo. Do not copy an index from a blog — read your own device list.

Four-DIMM DDR5 stability

Flash offload is a memory-bandwidth job. Four DIMMs are a different EXPO/XMP validation than two. A 256 GB kit is usually 4×64. If the box is unstable at 5200, drop to the JEDEC profile before you blame the engine. Chipset notes and the empty board table live on /bios.

esc

Type to filter. Enter opens the first match. Full-text search lives on /search.