Independent/Reader-funded/Infrastructure, not tokens
DeAINEWS

AI you control — open models, private inference, and the networks that run them.

PulseSelf-Hosting & Hardware

DeepSeek V4-Flash on a 64GB CPU box: a claim, not a result

llama-modchip claims a 284B DeepSeek V4-Flash quant runs CPU-only in 57.6GB RAM at 9-14 tok/s. All figures are author-reported and unreproduced.

DeAI is powered by Morpheus (mor.org). We cover competing providers on the same terms — see our methodology.

An open desktop PC tower on a wooden desk with RAM sticks installed and no graphics card, depicting the unverified llama-modchip claim that a 284B DeepSeek model can run on a 64GB CPU-only machine. Illustration: DeAI
An open desktop PC tower on a wooden desk with RAM sticks installed and no graphics card, depicting the unverified llama-modchip claim that a 284B DeepSeek model can run on a 64GB CPU-only machine. Illustration: DeAI

A project called llama-modchip is circulating on X and r/LocalLLaMA with a claim that would reset the hardware floor for open-weights inference: DeepSeek's 284B-parameter V4-Flash model running CPU-only on a 64GB machine. The repo is public and Apache-2.0 licensed, but every number in it is author-reported, and nobody has reproduced them yet.

Key facts

  • The llama-modchip README reports DeepSeek-V4-Flash (284.33B total, 13.17B active parameters) fitting in 57.61 to 58.9GiB of RAM at a 256K-token context on a 64GB machine, down from a 76.87GiB baseline, with zero swap.
  • Claimed throughput on a 16-core Zen 5 CPU with no GPU: 44.4 tok/s prefill and 9.1 to 14.7 tok/s decode, the upper end using a "Stockfish-PVS v2" speculative drafter.
  • The compression lever is a custom format called Fractal-64 at 1.71 bits per weight, with routed experts down to IQ1_S at 1.5625 bpw; stock llama.cpp, Ollama and LM Studio cannot load it.
  • The repo's own community leaderboard lists one entry from a second contributor, but the marquee 64GB figures remain the author's own runs.
  • The AI Weekly alert carrying the claim states plainly that no third party has reproduced the figures.

What's driving the conversation

The claim spread through self-hosting circles on both English and Chinese X, with a detailed breakdown from @TeksEdge walking through the memory math and kernel work, and a short summary from @RoundtableSpace reaching a wider audience. The pattern in replies is familiar: enthusiasm first, then the same caveat that these are developer-reported numbers, and CPU inference claims have a long history of shrinking under independent measurement.

Skeptics' strongest point is mechanical, not tribal: a 284B mixture-of-experts model only activates about 13B parameters per token, so the memory fit is plausible on paper. The bottleneck is memory bandwidth, and the claimed decode rates sit at the optimistic end of what 64GB DDR5 channels can sustain under realistic conditions. The README's answer is AVX-512 register tiling, a cache-stationary attention kernel, and speculative decoding borrowed from a chess engine's principal-variation search. That is exactly the kind of engineering that has produced real wins in the past, which is what makes it worth watching rather than dismissing.

The substance

Verified: the repo exists, the license is Apache-2.0, the quant format and configs are published, and the code can in principle be run by anyone with the hardware. Claims, not facts: every throughput figure, the "bit-exact lossless" assertion (1.00000 cosine similarity, 0.0000 KL-divergence against the full-precision reference), and the "+77% prefill / +53% decode" uplift numbers attributed to the kernel patches. The project's own paper and quality-gate benchmarks are self-published artifacts, not peer review.

The honest classification is: a well-documented unverified claim with a clear reproduction path. The artifact is inspectable, so this is not a hoax-shaped story, but it is also not a result until a second runner produces numbers. This is the same discipline we applied to the H200-hosting economics claim: interesting claim, named verification path, no planning decisions until it clears.

Why builders are watching

If the numbers hold under independent reproduction, the hardware floor for a frontier-adjacent open-weights model drops from multi-GPU rigs to a commodity desktop, which changes the economics in our self-hosting cost comparisons materially. If they do not, the story is still a useful template for how to evaluate the next such claim: check the repo license, check who ran the benchmark, check the context length, wait for a stranger's numbers. Anyone actually trying it should start with the project's hardware-check script and the smaller 30B variant before committing a weekend to the 284B quant. Until a second runner reports, treat this as watchlist material.

Questions

Can DeepSeek V4-Flash really run on a 64GB CPU-only machine?
Unverified. The llama-modchip project's README reports a 1.71-bits-per-weight quant of the 284B-parameter model fitting in 57.6 to 58.9GiB of RAM at 9.1 to 14.7 tokens per second decode on a 16-core CPU, but every figure is author-reported and no independent benchmark confirms it as of November 17, 2026.
What would verify the llama-modchip claims?
Three things: the project's published quant and config running on a second machine by someone unaffiliated, tokens-per-second measured at realistic context lengths rather than headline settings, and a community leaderboard entry from a contributor who does not share the author's hardware or affiliation.
Why is the claim hard to believe?
CPU inference on very large mixture-of-experts models is bottlenecked by memory bandwidth, and community attempts at DeepSeek V4-class models on CPU have historically come in far slower than initial reports once measured with real prompts and context.

Sources

  1. llama-modchip: run 284B DeepSeek-V4-Flash on 64GB CPU (project README) — GitHub (synchopate)
  2. llama-modchip runs 284B DeepSeek V4-Flash on 64GB CPU box — AI Weekly
  3. @TeksEdge breakdown of llama-modchip benchmarks — X
  4. @RoundtableSpace summary post — X

About DeAI

DeAI is an independent publication covering open-weight AI models, private inference, and decentralized infrastructure — the tools for running AI you actually control. We test providers on price, privacy, and refusal behavior and publish the numbers, not the vibes. DeAI is powered by Morpheus (mor.org), a decentralized inference marketplace, and covers it on the same terms as every other provider.

Powered by Morpheus and StrandCMS

Morpheus is a decentralized inference marketplace, covered on the same terms as every other provider — we rank it wherever the data lands. StrandCMS is the open-source, agent-first framework this site is built on.

Learn more about the Morpheus Inference API →

Sponsor disclosure — not editorial

Powered by Morpheus and StrandCMS. Morpheus is a decentralized inference marketplace, covered on the same terms as every other provider. StrandCMS is the open-source, agent-first framework this site is built on.

Learn more →