SCENE 11 / 24 · THE RUNTIME & MEMORY MANAGEMENT LAYER
End the fragmentation tax
Reserve exact blocks on demand instead of worst-case contiguous slabs.
TOKENS STORED · 0/64INTERNAL FRAG · 64 SLOTS
Contiguous reservation bets every request hits max context. Paging allocates 8-token blocks on demand — waste drops from whole slabs to less than one block per sequence.
ARCHITECTURE & FORMULATIONModule 4: The AI Runtime & Memory Management Layer
PagedAttention: virtual memory for attention
Pre-allocation reserves worst-case contiguous slabs per request; most sit empty, and fragmentation strands the rest. PagedAttention borrows the OS answer: fixed-size blocks allocated on demand, a block table mapping logical positions to scattered physical pages, and copy-on-write for shared prefixes.
Fragmentation Kill
Reserved-but-unused KV (internal fragmentation) plus unallocatable gaps (external) historically wasted 60-80% of KV memory. Paging cuts waste to under 4%.
Block Tables
Each request carries a table: logical block i → physical block. Attention kernels gather K/V through indirection instead of assuming contiguity.
Copy-on-Write Forks
Two requests sharing a prefix share physical blocks; divergence triggers copy. Beam search and n-best sampling become nearly free in memory terms.
With 16-token blocks, internal waste is <15 tokens per request regardless of context length. vLLM's paper reports 2-4× throughput over naive allocation purely from this.
REAL-WORLD PRODUCTION ENGINEERING
Block size is a tuning knob: 16 tokens (vLLM default) balances kernel overhead against fragmentation.
PagedAttention made beam search economically viable again — pre-paging, it was a memory multiplier.