HN.zip

From 300KB to 69KB per Token: How LLM Architectures Solve the KV Cache Problem

36 points by future-shock-ai - 3 comments
LuxBennu [3 hidden]5 mins ago
good overview of the architecture side but worth mentioning there's another axis that stacks on top of all of this: you can quantize the kv cache itself at inference time. in llama.cpp you can run q8 for keys and q4 for values and it cuts cache memory roughly in half again on top of whatever gqa or mla already saves you. i run qwen 70b 4-bit on m2 max 96gb and the kv quant is what actually made longer contexts fit without running out of unified memory. keys need more precision because they drive attention scores but values are way more tolerant of lossy compression, so the asymmetry works out.
az09mugen [3 hidden]5 mins ago
Unrelated, but 69KB is how much RAM Voyager 1 has.
gregman1 [3 hidden]5 mins ago
Voyager as a token of curiosity