Grafy News
Try Grafy free

Llama-modchip enables 284B DeepSeek model on 64GB RAM CPU

A new GitHub project called llama-modchip allows massive 284B parameter models to run on standard CPUs with 64GB of RAM, bypassing the need for high-end GPUs.

Illustration for the news story: Llama-modchip enables 284B DeepSeek model on 64GB RAM CPUSource: Hacker News — front page

A new open-source project is breaking traditional hardware barriers by allowing massive large language models (LLMs) to run on consumer-grade CPUs without the need for dedicated GPUs. The project, known as llama-modchip, enables the execution of the 284B parameter DeepSeek-V4-Flash model on machines equipped with only 64GB of RAM.

This development is significant because frontier-scale models typically require massive amounts of Video RAM (VRAM) found only in expensive enterprise-grade GPUs. By optimizing how these models interact with system memory and CPU architecture, llama-modchip provides a path for researchers and developers to run high-parameter models on standard workstations or even high-end laptops.

How does llama-modchip run massive models on a CPU?

According to the project's documentation on GitHub, the software achieves these performance gains through several specialized optimization pillars. One primary method is the use of Analytical SwiGLU-H2 Second-Order Hessian Compression, which helps shrink the memory footprint of the DeepSeek-V4-Flash model. Specifically, it reduces the model from a size that would typically cause an "out of memory" error on 64GB Linux systems down to approximately 56.56 GiB on disk.

To handle the actual computation, the project utilizes Fractal-64 MLA transcoding and a multi-level tiling strategy that spans the L1, L2, and L3 caches of the processor. This approach, combined with $L_2$-Quadrature MoE Pruning, allows the system to manage the massive workload across the CPU's architecture more efficiently than standard inference engines.

What kind of performance can users expect?

Performance varies depending on the hardware configuration, but the benchmarks provided by the developer show impressive results for a CPU-only setup. For the 284B DeepSeek-V4-Flash model, the project reports a prefill speed of approximately 44.36 tokens per second. During the decoding phase, users can see speeds ranging from roughly 9 to 14.7 tokens per second, depending on the specific optimizations applied.

For smaller Mixture-of-Experts (MoE) models, such as the 30B parameter versions, the speeds are even higher. The documentation states that the NVIDIA-Nemotron-3.5-30B-A3B can reach speeds between 25.0 and 60.4 tokens per second on a 16-core Zen 5 processor. On high-end 8-channel workstations like a Threadripper, the 30B MoE models can reach up to 111.62 tokens per second.

Which hardware configurations are supported?

The project is designed to scale across different tiers of consumer and professional hardware. For users with a standard developer laptop or mini-PC containing 16–32 GB of RAM, the project recommends running smaller models like the Nemotron-3.5-30B-A3B, which requires about 14.35 GiB.

A 64 GB desktop or server is the target for the full 284B DeepSeek-V4-Flash experience, as the peak memory usage (VmRSS) at a 256K context window is approximately 57.61 GiB. For those with hybrid setups—a CPU paired with a 16 GB GPU—the software can split the workload, keeping the "hot" attention trunk on the GPU while routing the "cold" MoE experts to the CPU's DDR5 memory.

Can this be used for AI coding and agents?

One of the standout features of llama-modchip is its ability to support agentic workflows. The project includes a feature called "Zero-API Claude Code restore." This is designed to eliminate the 45-second bottleneck often seen during CPU agent prompt re-evaluations.

By using a /dev/shm Slot-0 KV (Key-Value) warm restore, the system can restore the state of the model in as little as 13.1 to 32.6 milliseconds for the DeepSeek-284B model. This allows for much faster interaction when using the 40 tools associated with the Claude Code CLI, making local, CPU-based AI agents feel significantly more responsive.

How does this impact the local LLM ecosystem?

Historically, running "frontier" class models has been a privilege reserved for those with access to multi-GPU clusters. llama-modchip shifts this paradigm by proving that with advanced quantization and architectural tiling, high-parameter models can reside entirely in system RAM without relying on NVMe swap space.

This democratizes access to high-intelligence models for developers who may not have the budget for high-end NVIDIA hardware but possess significant system memory. It also encourages a move toward more efficient, specialized kernels that can squeeze maximum performance out of existing CPU instructions like AVX-512.

Applying local AI insights in Grafy

While llama-modchip is a specialized tool for local deployment, the principles of efficient model management and high-context window processing are central to modern AI development. For developers working on complex software projects, exploring how these models handle large codebases can be invaluable.

Users interested in the intersection of high-level AI reasoning and software engineering can utilize Grafy Code to build and test applications. While Grafy provides access to powerful cloud-hosted models through various providers, understanding the limitations and possibilities of local inference—as demonstrated by llama-modchip—can help developers better architect their local development environments and agentic workflows.

Frequently asked questions

Does llama-modchip require a GPU to run?

No, llama-modchip is specifically designed to run large models on a pure CPU. While it can support hybrid setups that use a small amount of GPU VRAM to accelerate certain tasks, its primary breakthrough is the ability to run massive 284B parameter models using only system RAM and the CPU.

Can I run the 284B DeepSeek model on a 32GB RAM laptop?

No, the 284B DeepSeek-V4-Flash model requires more memory than a 32GB laptop provides. According to the project, this specific model requires approximately 56.56 GiB of disk space and a peak memory usage of around 57.61 GiB to run effectively with a 256K context window.

What makes llama-modchip different from standard llama.cpp?

Llama-modchip uses custom optimizations that are not present in standard versions of llama.cpp or Ollama. These include Fractal-64 MLA transcoding, Analytical SwiGLU-H2 compression, and specialized tiling for L1/L2/L3 caches. Because of these custom tensor types, standard software will fail to open the models provided by this project.


Source: Hacker News — front page — Llama-modchip: 284B DeepSeek on 64GB RAM, no GPU