Loading video...

Video Failed to Load

Go Home

he made 405-billion-parameter models run on a single 8GB gaming GPU. instead of turning it into a paid service, he open-sourced the whole thing. Gavin Li Founder and CEO of Anima AI in the Bay Area. 'airllm' - it keeps one layer on the GPU at a time and...

111,308 views • 3 months ago •via X (Twitter)

37 Comments

Raichubuilds's profile picture
Raichubuilds3 months ago

37373737 seconds for 1 token?

leo's profile picture
leo3 months ago

not a new concept, but just practically useless for doing any real llm driven tasks due to how slow it is. Cool tho

0std | Pentester | AppSec's profile picture
0std | Pentester | AppSec3 months ago

hahahha another 0.12 tokens/s repo, good luck doing anything with such speed

O(1)'s profile picture
O(1)3 months ago

BS, every single token requires re-reading essentially the entire model off disk. A 671B model at 4-bit is 350GB.. per token. Real-world reports put it at 5–30x slower than proper full-VRAM inference and 50–200x slower than APIs seconds-per-token or worse, with CPU pinned at 100%

Herminia's profile picture
Herminia3 months ago

808 seguidores, 22.700 estrellas. La asimetría entre quién construye y quién tiene atención es casi más interesante que el logro técnico.

Le bureau Virtuel's profile picture
Le bureau Virtuel3 months ago

Merci à lui

Atenov int.'s profile picture
Atenov int.3 months ago

i trust what was actually built into airllm

dunik's profile picture
dunik3 months ago

yes, this project it's amazing

Abhishek Shinde's profile picture
Abhishek Shinde3 months ago

I guess github is the new place for AI research

AIAIO's profile picture
AIAIO3 months ago

One would think 800 followers isn't that much for a project that seems to solve some of the biggest pain points of local AI. How fast does this thing run? More of a proof of concept or actually usable? I recall the port of a Linux kernel in a small 8 bit pic using emulation. Great idea. Just not usable.

Alex's profile picture
Alex3 months ago

Never seen this GitHub before. I'll dig into it

dunik's profile picture
dunik3 months ago

yep, start doing it right now!

DEV 0x***(Full Stack)💾's profile picture
DEV 0x***(Full Stack)💾3 months ago

for me when i hear "bay area" i run and never look back lol

Dany Boy's profile picture
Dany Boy3 months ago

it's not a "crazy" new thing. It's been doable from day 1. The problem with this is speed, concurrency, KV heads, quants etc. It all makes the model unusable for any real work.

0xSlyth's profile picture
0xSlyth3 months ago

absolute madman to share this openly

SubThought Corp's profile picture
SubThought Corp3 months ago

He didn't specialize on one content area for a target market. That was his mistake. Start with Finance or Real Estate next try.

porto4mil's profile picture
porto4mil3 months ago

@eltuganomics

🤯's profile picture
🤯3 months ago

1 tok/week

Dimuth Kurukula's profile picture
Dimuth Kurukula3 months ago

@grok how is the approach here different from calibri for glm5.2

Chuck Petras's profile picture
Chuck Petras3 months ago

@BrianRoemmele

nanobro🎈's profile picture
nanobro🎈3 months ago

Wen glm5.2 in dgx spark

🅰🅽🆂🅷🆄🅻 🆂🅸🅽🅶🅷's profile picture
🅰🅽🆂🅷🆄🅻 🆂🅸🅽🅶🅷3 months ago

1token per day?

Shesaidmewakeup's profile picture
Shesaidmewakeup3 months ago

AirLLM is exactly the kind of tool that lets you get the most out of low-end hardware. That guy is really impressive. 🔥

AI Mastery Guide's profile picture
AI Mastery Guide3 months ago

Fitting a 671B model into 12GB is a genuinely wild feat

Andrius Mostauskas's profile picture
Andrius Mostauskas3 months ago

Will this work with LM Studio?

knopka_web3's profile picture
knopka_web33 months ago

Вы не проверяли что это за Airllm этот инструмент не работает.

Jörg Kachelofen's profile picture
Jörg Kachelofen3 months ago

Have fun…

Qedge's profile picture
Qedge3 months ago

airllm streams one layer at a time from cpu to gpu. That layer-wise swap gives us a clean hook for quantum-inspired prefetch on next token path.

Anotos's profile picture
Anotos3 months ago

No. This thing is utter bullshit and is WAY too slow to be useful AT ALL. It generates a token PER MINUTE.

David's profile picture
David3 months ago

@midudev

Young Sneed's profile picture
Young Sneed3 months ago

holy based! where GGUF? chapeau to the legend open sourcing this!!

Nahid's profile picture
Nahid3 months ago

airllms layer streaming is a wild approach

Marshall's profile picture
Marshall3 months ago

How many seconds per token 😂

Ella Smith's profile picture
Ella Smith3 months ago

This is amazing, we really need efficient LLMs now. Benchmarks should start talking about that now.

Shara's profile picture
Shara3 months ago

Open sourcing instead of monetizing that breakthrough is a generous move.

SubThought Corp's profile picture
SubThought Corp3 months ago

Why?

Saman Ahmed's profile picture
Saman Ahmed3 months ago

I love these cases where one clever engineering choice changes who gets access to a technology.

Related Videos

UC Berkeley just open-sourced FreeToken. (2–4x faster local LLM inference than Ollama) the results are wild: - Qwen3.6-35B on an 8GB GPU at 39.3 tokens/s - DeepSeek-V4-Flash 284B on a 32GB GPU at 22 tokens/s - GLM-5.2 753B on a 96GB GPU at 14.9 tokens/s a 35B model at 16-bit precision needs about 70GB just for its weights. even at 4 bits it is close to 18GB, and FreeToken serves it on an 8GB GPU. let me explain how: all three models mentioned above are Mixture-of-Experts, and that is what FreeToken takes advantage of. each layer holds hundreds of separate experts plus a small router that picks a few of them per token. Qwen3.6-35B activates roughly 3B of its 35B parameters per token. DeepSeek-V4-Flash picks 6 of 256 experts per layer, so 13B of its 284B run at a time. so compute was never the bottleneck. the weights a single step touches fit comfortably on a consumer GPU. every expert the router might pick still has to exist somewhere. they sit in system RAM, and the GPU keeps a cache of the ones the model has been using recently. so everything comes down to what happens when the router picks an expert that is not on the GPU. there are two ways to serve that miss: 1. copy it over PCIe and run it on the GPU 2. run it on the CPU, where it already lives both read from the same system memory, so they compete for one pool of bandwidth instead of adding to each other. existing engines pick one option and freeze it when the model loads. but routing changes on every token, so a fixed choice misses most of what the model asks for. FreeToken measures both bandwidths on your machine and splits each step's misses between the two paths in proportion. the GPU and CPU results then merge exactly, with no approximation. two machines with the same GPU can end up wanting opposite strategies, which I did not expect. a 5090 in a gaming desktop should push nearly everything over PCIe, while an 8GB laptop is better off computing most misses on the CPU. none of that is readable off a spec sheet, so the engine profiles it once per machine. the second half of the design is about agents. coding agents constantly rewrite their own history, and every edit normally forces thousands of tokens back through prefill. FreeToken saves its checkpoints at the exact boundaries agent frameworks cut on, so it only reprocesses the new part. its slowest first token stays under 44 seconds, while llama.cpp peaks at 232 and KTransformers at 946. it serves the OpenAI and Anthropic APIs under Apache 2.0, so Claude Code and Codex can point at it directly. releasing weights publicly decides who can download a model, not who can afford to run one. frontier open models keep shipping, and running them still assumes a rented cluster. meanwhile there are over a hundred million consumer machines with discrete GPUs sitting mostly idle. closing that gap was never a hardware problem, and work like this is what turns open weights into something you can actually use. paper: repo: almost every idea in this post, from why memory bandwidth decides the outcome to why moving weights costs more than computing on them, comes straight out of how a GPU is built. I wrote a detailed primer on that. the article is quoted below.

Akshay 🚀

345,385 views • 2 months ago