RAMen Back to RAMen

How RAMen works

Local AI gets frustrating on long work for two reasons. The model slows down as a conversation grows. And when you close the app, everything it had read is gone, so reopening a long chat means waiting while it reads the whole thing again. RAMen fixes both, on your own computer, in front of llama.cpp.

A replay of a real run at its real speed: Qwen3 32B on an RTX A6000, the same 87,099-token conversation, normal llama.cpp on the left (8.4 tokens per second) and RAMen on the right (20.5). Same answer.

1. Chats that come back in seconds

While a model reads a conversation it builds a working memory (the KV cache). RAMen saves each conversation's working memory to disk as you go and restores it the moment that conversation continues, even after a restart. Many chats and agents share a few live slots on the GPU; the rest wait on disk and come back on demand.

Real recording, real time, on a Mac mini M2 Pro with Qwen3 4B: a 70,082-token chat, restarted. Reading it from scratch took 12 minutes 47 seconds just before; RAMen restored it and wrote the first word after 3.7 seconds. A second take, with the Mac's file cache cleared first so the saved chat had to come from the SSD, wrote the first word after 3.0 seconds.

Saving the cache is not a new idea: llama.cpp has slot save and restore, and small tools automate it. How to do it by hand. RAMen does it for every session automatically, with checks that a saved cache matches the model and settings before it is reused, and it combines it with the speedup below.

2. Long chats that stay fast

Normally every new word the model writes reads the whole working memory, so a 100,000-token chat is several times slower than a short one. RAMen keeps a small summary of each block of the memory and, at each step, reads only the blocks that matter for the next word (about 8,000 tokens' worth), plus the start and the most recent part of the conversation. The idea comes from research on query-aware sparse attention (Quest, 2024). RAMen builds it into llama.cpp for NVIDIA and Apple GPUs. It switches on by itself only past the length where it is faster on your kind of machine (between 16K and about 43K tokens), so it is never slower.

Quality: when the selection covers the whole conversation, RAMen writes exactly the same text as normal attention. With selection on, it gave the same answers as full attention in 54 of 54 long-document tests (16K to 64K tokens), and a needle-in-a-haystack test passed at 32K and 64K.

Measured results

Machine and modelConversationCacheNormal llama.cppRAMenFaster
RTX A6000, Qwen3 32B87K tokens8-bit8.4 tok/s20.4 tok/s2.4x
RTX A6000, Qwen3 32B56K tokens8-bit11.5 tok/s20.9 tok/s1.8x
RTX 4090, Qwen3 4B224K tokens8-bit31 tok/s88 tok/s2.9x
NVIDIA L4, Qwen3 4B128K tokens16-bit9.1 tok/s42.2 tok/s4.6x
NVIDIA L4, Qwen3 4B128K tokens8-bit8.5 tok/s35.1 tok/s4.1x
Mac mini M2 Pro 16 GB, Qwen3 4B81K tokens8-bit7.4 tok/s22.6 tok/s3.1x
Reopening a saved chatSizeReading it againRAMen
Mac mini M2 Pro, Qwen3 4B69,864 tokens12.7 minutes3.7 seconds
NVIDIA L4, Qwen3 4B104,744 tokens220 seconds1.8 seconds
RTX 4090, Qwen3 4B197,860 tokens91 seconds5.6 seconds

Writing speed (decode), same model, settings and cache type on both sides, November 2026. Below about 30K to 40K tokens a fast NVIDIA card gains little, and RAMen keeps normal attention there.

Limits, honestly

Try it

A fresh install on a Mac mini, recorded as it happened (the model download is shown 4x faster).

Mac and Linux: curl -fsSL https://getramenai.com/install.sh | bash
Windows (PowerShell): irm https://getramenai.com/install.ps1 | iex
Then ramen start. The free plan is free forever, and every install starts with 14 days of everything. See plans.