Discontinued Intel Optane Memory Runs 1 Trillion Parameter LLM Locally at 4 Tokens/Sec
Original: Computer build using Intel Optane Persistent Memory - Can run 1 trillion parameter model at over 4 tokens/sec View original →
The Build
A post on r/LocalLLaMA detailed a custom system using Intel Optane Persistent Memory (PMem) to run Kimi K2.5 - a 1 trillion parameter model - locally at over 4 tokens per second. The post gathered 677 upvotes, with the community particularly interested in the novel use of discontinued hardware.
What Intel Optane PMem Is
Intel Optane Persistent Memory is a DIMM-form-factor module that sits between DRAM and SSDs in the memory hierarchy. Intel discontinued the product line, which means secondhand Optane sticks are now available at a fraction of equivalent DRAM capacity costs. This builder assembled 768GB of effective RAM using PMem in Memory Mode, where the Optane serves as system RAM with standard DRAM sticks acting as a cache layer.
How the Model Runs
Kimi K2.5's mixture-of-experts (MoE) architecture made it well-suited for this setup. Using llama.cpp's hybrid GPU/CPU inference, the builder placed attention weights, the dense layer, and shared expert components on a 12GB GPU, with the bulk of sparse expert weights living in the Optane PMem.
Why This Matters
Running trillion-parameter models locally has until now required datacenter-class hardware. This build demonstrates that creative use of secondhand discontinued hardware can bring that capability to a single workstation, opening a path for more researchers to work with frontier-scale models locally.
Related Articles
A LocalLLaMA build with five RTX PRO 6000 cards and a 5090 made the practical cost of serious local inference hard to ignore.
A high-engagement r/LocalLLaMA thread reports strong early results for Qwen3.5-35B-A3B in local agentic coding workflows. The original poster cites 100+ tokens/sec on a single RTX 3090 setup, while comments show mixed reproducibility and emphasize tooling, quantization, and prompt pipeline differences.
A March 2026 r/LocalLLaMA post with 126 points and 45 comments highlighted a practical guide for running Qwen3.5-27B through llama.cpp and wiring it into OpenCode. The post stands out because it covers the operational details that usually break local coding setups: quant choice, chat-template fixes, VRAM budgeting, Tailscale networking, and tool-calling behavior.