ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial2 min readDisconfirmAI Editorial

c't Reporter Tests Local LLMs: Memory Bandwidth, Not Compute Power, Determines Generation Speed

c't reporter Jan-Keno Janssen's hands-on tests of local large language models on the RTX 4090, RX 9070 XT, Intel Arc Pro B70, Mac Studio M5 Ultra, and AMD Strix Halo show that token generation speed is primarily determined by memory bandwidth. DDR5-5200 is more than 12 times slower than GDDR6X, explaining the massive gap between CPU and GPU inference. The Mac matches the 4090 during the generation phase but processes long prompts at less than one-third its speed—both phases require attention for coding agent workflows.

2026-11-07 00:27 GMT+8

In a video published in November 2026, c't magazine reporter Jan-Keno Janssen released a series of hardware benchmarks for local large language models, with the core finding being that the data transfer rate of memory—not the floating-point compute power of the GPU—determines token generation speed. Using the standard llama.cpp tool to test Qwen 3.8-27B (Q4_K_M quantization), the RTX 4090 achieved 51.1 tokens per second, whereas running CPU inference on the same machine using only DDR5-5200 memory resulted in an output so slow it was visibly character-by-character—a difference of about 15 times. He explicitly pointed out that DDR5-5200 has a bandwidth more than 12 times slower than the 4090's GDDR6X, a ratio that largely corresponds to the difference in inference speeds.

This mechanism explains the practical trade-offs different hardware platforms face in coding agent workflows. The Mac Studio M5 Ultra (with 256GB of unified memory) is nearly on par with the RTX 4090 during the token generation phase, but achieves less than one-third of its speed during prompt processing (reading long code or documents): while the 4090 reads about 4,000 tokens of video text in just over a second, the Mac takes about 4 seconds. This makes little difference for pure chat, but coding agents need to repeatedly read codebases and documentation, meaning bottlenecks fall on bandwidth and compute power respectively. Although the AMD RX 9070 XT (€920, 16GB VRAM) ran at 34.4 tokens per second, the weights for Qwen 3.8-27B plus context almost completely filled the VRAM, leaving only about 8K tokens of usable context. It cannot simultaneously support image recognition and the 60K+ context required for coding agents—meaning it can run benchmarks but struggles with actual workloads.

Sign in / Sign up
ReadingResearchRadarInvestment framework

Janssen's practical rule is: when choosing hardware, look at memory bandwidth first, then capacity. GPUs with 24GB or 32GB of VRAM can hold both model weights and sufficient context; unified memory systems should have at least 48GB to leave room for OS and other software overhead. The Intel Arc Pro B70 (32GB, currently priced above €1,700) generates at about half the speed of the 4090, but offers ample capacity and supports ComfyUI image generation. The AMD Strix Halo (128GB unified memory, under €4,000) has a raw generation speed of only 13.3 tokens per second, but enables speculative decoding to boost performance to over 40 in code generation scenarios, and even exceeds 100 in code reproduction scenarios. All data are self-tested by the author using the llama-bench tool from llama.cpp under standard parameters, without independent replication.

Sources

  • heise.dec't Magazin↗
Continue researching →