Unverified50% confidenceFactExact time
Betelgeuse uses a RAM victim cache plus an io_uring pager to reduce physical NVMe reads from about 71 MB/token to 12.43 MB/token.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/31/2026
First Seen
Valid until: 1/29/2027
Sources
Running a 68GB Large Model on a 12GB GPU: Betelgeuse Engine Benchmarked at 22 tok/s
redditr/LocalLLaMA10/31/2026
Related Entities
Related Claims
UnverifiedA user running a Threadripper platform with 512GB DDR4 memory achieved approximately 8 tokens/s running DeepSeek 671B by offloading expert layers to RAM.70% similarUnverifiedThe author's test machine is configured with Debian 13, an Intel Core Ultra 9 185H, 32GB DDR5, and a 1TB NVMe reading at about 5.7 GB/s.69% similarUnverifiedWhen the model loads, it first allocates a full-precision shell of approximately 1.29 GB and then reads in 643 MB of full weights, with peak memory potentially reaching approximately 3,400 MB.68% similarUnverifiedThe 28.8 GB N-gram interpolation table resides on the hard drive, occupying neither VRAM nor memory.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1120768API
curl https://kongchang.com/api/v1/knowledge/claims/1120768MCP
get_claim(id=1120768)