Real Long-Term Memory for AI: A 50-Million-Token Window That Is Faster and Cheaper Than Recompute
Sietse Schelpe
Corbenic AI
Published October 7, 2026 · on the feed October 8, 2026 · ▲ 9 · arXiv 2610.10845
The abstract
A large language model can only use the text that fits in its context window, and it recomputes its internal key-value (KV) state for a prompt every time the prompt is sent. We test a memory layer, the public package galahad-kv, that saves the KV state of each block of about 16,000 tokens to encrypted local NVMe disk and loads it back later, byte-exact, without recomputing it. We ran it on 50,000,000 tokens of real public text, served through vLLM on one NVIDIA H100, with Gemma 4 12B and Gemma 4 31B. Every block we probed was loaded back from the encrypted store with no recompute (100 of 100, at depths from 0 to 50M tokens) on both models. Loading a block was 2.8x to 4.3x faster than recomputing it and used 8.8x to 12.3x less GPU energy, and GPU memory stayed flat over the whole 50M-token stream. Asked about facts planted millions of tokens earlier, the 12B model gave the right answer 82 times out of 100 and the 31B model 98 times out of 100. Neither model made up an answer. The limits are as follows. This is reuse of stored state, not a wider attention window: one block is loaded at a time, and how well a question is answered depends on the model. Writing the memory is a one-time cost, and the store takes terabytes of local NVMe disk. We describe the test protocol, which is built to resist common ways of gaming long-context benchmarks, and give a single-GPU reproduction that uses public software and a free licence for the package.
The Brief
2:30A short podcast summary of the paper. Written and voiced by AI.
Transcript
Real Long-Term Memory for AI. A 50-Million-Token Window That Is Faster and Cheaper Than Recompute. By Sietse Schelpe, from Corbenic AI. Published on the seventh of October.
A large language model can only use the text that fits in its context window, and every time a prompt is sent, the model recomputes its internal key-value state for it from scratch. The claim tested here is that this recompute can be replaced by storage. The memory layer under test is a public package called galahad-kv. It saves the key-value state of each block of about sixteen thousand tokens to encrypted local NVMe disk, and loads it back later, byte-exact, without recomputing it. The paper's title states the claim plainly: that this is faster and cheaper than recompute.
The test ran fifty million tokens of real public text through vLLM on a single NVIDIA H100, with two models: Gemma four at twelve billion parameters and Gemma four at thirty-one billion. Every block that was probed came back from the encrypted store with no recompute, one hundred out of one hundred, at depths ranging from the start of the stream to fifty million tokens in, and that held on both models.
Loading a block was between two point eight and four point three times faster than recomputing it, and used between eight point eight and twelve point three times less GPU energy. GPU memory stayed flat over the whole stream.
Then came recall. Asked about facts planted millions of tokens earlier, the smaller model answered correctly eighty-two times out of one hundred, and the larger model ninety-eight times out of one hundred. Neither model made up an answer.
The author is explicit about the limits. This is reuse of stored state, not a wider attention window. Only one block is loaded at a time, so the fifty million tokens are not all attended to at once, and how well a question is answered depends on the model, as the gap between the two recall results shows. Writing the memory is a one-time cost. And the store is not small: it takes terabytes of local NVMe disk.
The protocol is described in full, and it is built to resist common ways of gaming long-context benchmarks. A single-GPU reproduction is provided, using public software and a free licence for the package.
What the result trades is compute for disk. Instead of paying again to rebuild the key-value state of text the model has already processed, the state is written once, kept encrypted on local storage, and read back exactly when it is needed. The measured payoff is speed, energy and flat GPU memory, and the price is terabytes of disk and a model that sees one stored block at a time.
More with an account
Listen to every day’s papers
Daily playlists, deep dives, quests for the papers, and quizzes on their key terms.
Join free