Google's experimental model replaces sequential autoregressive decode with parallel denoising on a 256 token canvas, fitting a quantized 26B parameter MoE inside 18 GB of VRAM and reporting throughput of up to 1,000+ tokens per second on a single H100, vendor figures that redraw…
Google's DiffusionGemma developer guide lands as an experimental model with an unusual bet for a text LLM: stop decoding tokens one at a time and denoise the entire output block in parallel. The result, if Google's vendor numbers hold up under third-party testing, is a local-serving story that turns the usual autoregressive tradeoff on its head. The bottleneck shifts from memory bandwidth to raw compute, the active parameter count drops to a fraction of the headline 26B, and the hardware a developer reaches for changes with the workload.
The model is a 26B-parameter Mixture-of-Experts built on the Gemma 4 backbone that activates only about 3.8B parameters per token, according to the guide. That sparsity is the first thing to register for local-LLM developers. With aggressive quantization, the guide says the model fits inside an 18 GB VRAM budget, which is the size class of a single consumer flagship card. A dense 26B would be a different conversation; a 3.8B-active MoE inside the same memory envelope is genuinely a different category of cost.
The mechanism is block-wise diffusion rather than the usual token-by-token autoregressive decode. The guide describes a 256-token canvas that the model evaluates with bidirectional attention, refining the whole block simultaneously and committing the result to the KV cache before starting a fresh canvas conditioned on the committed history. That hybrid is the real story. Long outputs do not have to come out of a single denoising pass, but each pass produces a meaningful chunk of text in parallel. The wire copy will lead with the headline throughput; the technical shift underneath is what a Type0 reader needs to evaluate.
On throughput, the DiffusionGemma guide reports up to 700+ tokens per second on an NVIDIA GeForce RTX 5090 and 1,000+ tokens per second on a single NVIDIA H100, with a 4x speedup claim relative to autoregressive baselines on the same hardware. The numbers are vendor-reported, with no independent third-party benchmark in the source set, and the model is explicitly labeled experimental. Treat the figures as conditions-of-measurement rather than universal wins: the speedup depends on a parallel-friendly workload, tensor-core-rich hardware, and the kernel support the model gets from the serving stack. A developer running a low-batch, latency-sensitive single-stream inference pattern will not see the 4x.
The right workload for DiffusionGemma, as the guide frames it and as the architecture implies, is batch-style or structured generation that fills the 256-token canvas with useful work. A Sudoku-style constrained task is the showcase because every candidate is a multivariable constraint, and parallel denoising can prune many of them at once. That is illustration, not a general capability claim, and it should be read that way. The same canvas shape is what makes things like long-form code generation, structured data extraction, or batch prompt evaluation interesting candidates. Streaming a single token at a time into a chat UI is not what this model is built to do well.
The developer-facing question is whether the model is worth pulling into a local stack today. The guide positions DiffusionGemma as a companion to a prior launch announcement and as a path into the Gemma 4 tooling family. That is meaningful: it inherits the surrounding ecosystem rather than asking a developer to start over. Against that, the experimental label, the vendor-only performance evidence, and the absence of a published technical paper in the current source set push toward evaluation rather than production adoption. The honest answer is that this is a workload-fit question, not a speedup question, and the answer depends on whether the developer's serving pattern matches the canvas.
What to watch next: the technical paper or model card, and the first independent reproductions of the throughput numbers. Those will determine whether DiffusionGemma is a real shift in local-inference economics or a DevRel showcase that compresses back into the autoregressive baseline once the marketing conditions are stripped out.