YOU ARE VIEWING ONE ITEM FROM THE AICRIER FEED

Qwen3.6-35B-A3B hits 79 t/s, 128K ctx

AICrier tracks AI developer news across Product Hunt, GitHub, Hacker News, YouTube, X, arXiv, and more. This page keeps the article you opened front and center while giving you a path into the live feed.

// WHAT AICRIER DOES

7+

TRACKED FEEDS

24/7

SCRAPED FEED

Short summaries, external links, screenshots, relevance scoring, tags, and featured picks for AI builders.

Qwen3.6-35B-A3B hits 79 t/s, 128K ctx
OPEN LINK ↗
// 45d agoBENCHMARK RESULT

Qwen3.6-35B-A3B hits 79 t/s, 128K ctx

A Reddit benchmark shows Qwen3.6-35B-A3B running at 78.7-79.3 tokens/sec on an RTX 5070 Ti when llama.cpp uses `--n-cpu-moe` instead of the default `--cpu-moe`. The setup also claims 128K context is practical with `-np 1` and q8 KV cache settings.

// ANALYSIS

This reads less like a model breakthrough and more like a reminder that MoE placement policy can make or break local inference. On 16GB GPUs, the difference between keeping experts pinned to CPU versus splitting them intelligently is the difference between wasting VRAM and getting a genuinely usable speedup.

  • `--cpu-moe` leaves most of the GPU underutilized; `--n-cpu-moe 20` pushes the later experts onto VRAM and roughly jumps generation from 51.2 t/s to 78.7 t/s.
  • `-np 1` matters for single-user serving because it avoids wasting memory on extra recurrent-state slots, which helps make the 128K context claim believable in a constrained setup.
  • The result is hardware-specific, but the pattern is useful: for sparse MoE models, inference tuning can matter as much as quantization choice.
  • The 9800X3D’s large L3 cache probably helps the CPU side, so this is not a universal 16GB-GPU recipe, just a strong data point for consumer desktop rigs.
// TAGS
qwen3-6-35b-a3bllmgpubenchmarkinferenceopen-source

DISCOVERED

45d ago

2026-04-18

PUBLISHED

45d ago

2026-04-18

RELEVANCE

10/ 10

AUTHOR

marlang