Fetching from the wire…
Infra2026-08-02 · source-backed
sqliteai/waste (769 stars, created July 28) keeps only K3's 27.28GB trunk resident and streams the ~4% of experts activated per token off SSD, opening the undistilled model in 29.06GB of RAM. The counterintuitive result is the cache table: raising the expert cache from 17.32GB to 23.32GB lifts hit rate from 36.2% to 38.4% while throughput collapses eightfold, because a cache hit becomes a page fault. Storage bandwidth is binding: a cold token reads ~17GB of experts, and a USB enclosure at 0.94 GB/s versus internal NVMe at 12.78 GB/s is the difference between working and not. Layers validate against PyTorch to 3.6e-06 on final logits.
Each link below shares sources, entities, or timing with this story.
Kimi K3 built by Moonshot / Shared entity: Kimi K3 / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Kimi K3 built by Moonshot); both cover Kimi K3; reported by the same outlet (github.com).
Kimi K3 built by Moonshot / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Kimi K3 built by Moonshot); both cover July, Kimi K3; overlapping topics (cache, expert).
Kimi K3 built by Moonshot / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (Kimi K3 built by Moonshot); both cover July, Kimi K3; earlier July coverage from 2026-07-25.
Kimi K3 competes with OpenAI / Shared entities / Same source domain
Linked by a graph relationship (Kimi K3 competes with OpenAI); both cover July, Kimi K3; reported by the same outlet (github.com).
Kimi K3 benchmarked against B300 / Shared entities / Tension
Linked by a graph relationship (Kimi K3 benchmarked against B300); both cover Kimi K3, PyTorch; pushes against this story (against).
Kimi K3 built by Moonshot / Shared entities / Earlier coverage
Linked by a graph relationship (Kimi K3 built by Moonshot); both cover July, Kimi K3; earlier July coverage from 2026-07-30.
Kimi K3 uses NoPE / Shared entities / Earlier coverage
Linked by a graph relationship (Kimi K3 uses NoPE); both cover July, Kimi K3; earlier July coverage from 2026-07-29.
Kimi K3 benchmarked against Fable / Shared entities / Earlier coverage
Linked by a graph relationship (Kimi K3 benchmarked against Fable); both cover July, Kimi K3; earlier July coverage from 2026-07-26.