Dr Plan L ∞/21M ♽ retweeted
> Fable 5.2 designed 3 devices
> one simple prompt per device
> built its own router in 30 minutes
> each board less than a day
> all 3 worked fine
hardware design is gonna be super fun in the next few years!
Dr Plan L ∞/21M ♽ retweeted
hey @grok the ants don't get diabetes?
Dr Plan L ∞/21M ♽ retweeted
Visitor: "Where's the fruit? Gorillas eat fruit."
Keeper: "Not here. We took it off the menu in 2014. Most big zoos have since."
Visitor: "Why would you take fruit off a gorilla?"
Keeper: "Because it isn't fruit any more. Everything in a supermarket's been bred for a century to be sweeter. A wild fig's about as sweet as a carrot. A supermarket banana's a pudding."
Visitor: "And the gorillas?"
Keeper: "Got fat. Teeth went. Two of the males were pre-diabetic. The vet said feeding them modern fruit was like feeding them chocolate bars with the wrapper left on."
Visitor: "What do they get now?"
Keeper: "Leaves, stems, a bit of veg. They sulked for a fortnight and lost the weight."
Visitor: "So the fruit was too sugary for a 180-kilo animal built to eat it."
Keeper: "That's the paperwork, yes."
Visitor: "I've got a bag of grapes in the buggy for my two-year-old."
Keeper: "Lovely. We'd not be allowed to give those to the chimps."
Dr Plan L ∞/21M ♽ retweeted
Someone wrote a bash script that emails Sam Altman every day their RAM sits idle on a Linux box.😄
It's a reply to what Altman said on John Collison's Cheeky Pint podcast on Oct 29:
"From a global allocation perspective, actually, it's quite terrible to have everybody have a bunch of the world's limited supply of DRAM sitting in their own computer, and being used maybe 5% of the time."
The project is called Ram-Altman. A cron job reads /proc/meminfo every five minutes and counts used memory as MemTotal minus MemAvailable. If more than 10% of RAM is free, Altman gets one email a day with the real figures.
Dr Plan L ∞/21M ♽ retweeted
llama.cpp merged something big for Localmaxxers whose AI models don't fit in VRAM. 👀🔥 (Strata has this too)
The upgrade is pure software and no expensive or hard-to-find new GPU needed.
PR #30966 merged November 7.
Here's what they've added.
When you run a huge Mixture-of-Experts (MoE) model that doesn't fit in GPU memory, llama.cpp can cache frequently used experts in VRAM.
But what happens when the model needs an expert that ISN'T in the cache?
Previously, the MoE cache path would upload that expert's weights from system RAM into GPU VRAM for execution.
That means transferring potentially large amounts of data across PCIe.
Now llama.cpp has another option.
Run some of those missing experts directly on the CPU! This is important especially when running models on eGPU (low bandwith thuderbolt)
No need to transfer their full weights into VRAM first.
Okay, so what?
The developer tested Qwen3.8-Flash-Next IQ4_NL with approximately 6.3GiB allocated to the GPU expert cache.
⚡ GPU uploads only → 24.2 tps
🚀 CPU handles 95% of cache misses → 47.6 tps
That's 96.7% FASTER decoding!
And an RTX 3090 user tested Qwen3.8-Flash-Next UD-IQ4_XS with a 5.5GiB GPU cache.
🐌 GPU uploads only → 19.5 tps
🚀 CPU handles 95% of misses → 31.8 tps
Approximately 63% faster on the same RTX 3090!
Now here's the clever part.
The developers also added an automatic tuning script.
It measures and evaluates combinations of:
💾 GPU expert-cache size
🧠 CPU execution share
⚡ Expert-cache hit rates
🔄 CPU/GPU transfer performance
And recommends settings for your hardware.
Because more CPU offloading isn't always faster.
With a larger ~19GiB GPU cache, the developer measured these
⚡ GPU uploads only → 65.5 tps
🚀 50% CPU miss share → 66.4 tps
🐌 95% CPU miss share → 54.1 tps
See what happened?
The best strategy changes depending on how much VRAM is available and how fast the CPU, GPU and memory can move and process data.
And to be clear, 95% CPU miss share does not necessarily mean the CPU runs 95% of the model.
It means the CPU handles approximately 95% of eligible GPU cache misses, while cached experts still execute on the GPU.
Your CPU and system RAM aren't just places to park model weights now. More regular RAM is better.
They can actively help execute the model when moving those weights would be slower.
And now this capability is merged into upstream llama.cpp.
Free. Open source. No new GPU required. 🔥
Link in ALT.









































