@seclink: There are a few obvious interview questions: 1. Can Transformer do large-model inference? It can, so why not use it, and why must we use sglang and vllm? - Essentially because Transformer's performance is too poor; the bottlenecks are memory (KV cache) and slow token-by-token decoding...

X AI KOLs Timeline News

Summary

Discusses the bottlenecks of using Transformer for large-scale inference and reviews the evolution of inference optimization technologies for large models from 2023 to 2026, including KV cache quantization, speculative decoding, architectural innovation, and hardware-software co-design.

There are a few obvious interview questions: 1. Can Transformer do large-model inference? It can, so why not use it directly, and why must we use sglang and vllm? - Essentially because Transformer's performance is too poor; the bottlenecks are memory (KV cache) and slow token-by-token decoding. - Back in 2023, everyone was still making incremental innovations on Transformer, such as attention with shared KV heads, and FlashAttention using I/O awareness to reduce HBM reads/writes; on quantization and pruning, weights were compressed to 4-bit; on speculative decoding, small models propose and large models verify; on architecture, DeepSeekMoE does sparse activation, and PagedAttention does paged management of KV to eliminate storage fragmentation. 2. In 2024, quantization extended to KIVI/QServe (compressing KV cache to 2-4 bits to specifically address the context memory wall), and FP8 became native on Hopper; multi-head decoding heads were added to avoid external draft models; on the scheduling side, RadixAttention became standard (prefix reuse technology), and continuous batching and chunked prefill became standard. 3. In 2025-2026, software and hardware became integrated. The paradigm is to make models inherently suitable for inference starting from the training phase. Model architecture and GPU features are designed together: attention goes from MLA (DeepSeek-v3's breakthrough) to NSA (hierarchical sparse matrix); EAGLE-3 (feature-level draft), MTP (self-speculation, saving even the draft [thinking process]). 4. Quantization uses NVFP4 (hardware support, performance improvement). 5. PD separation (further reduces costs by 30-40%). Overall, the evolution of large-model technologies is closely related to the actual division of work in big companies. Any problem can be solved by categorizing, layering, and prioritizing. Performance waste and similar issues can be gradually refined to squeeze out cost-effectiveness.
Original Article
View Cached Full Text

Cached at: 08/05/26, 06:27 PM

There are a few obvious interview questions:

  1. Can Transformers handle large model inference? Yes, they can, so why not use them directly, but instead have to use sglang, vllm?

    • Actually, at its core, it’s still because Transformer performance is just too underwhelming, with bottlenecks in VRAM (KV cache) and slow token-by-token decoding.
    • Going back to 2023, everyone was still tinkering with minor innovations on Transformers, like shared attention KV heads, FlashAttention using IO-awareness to save HBM reads/writes; on quantization and pruning, squeezing weights down to 4bit; on speculative decoding, small models guess, large models verify; architecturally, DeepseekMoE with sparse activation, pagedattention for paged KV management to eliminate storage fragmentation.
  2. In 2024, quantization extends to KIVI/Qserve (compressing KV cache to 2-4bit, tailored for the context VRAM wall), FP8 natively bare on Hopper; enhancements bring multi-head decoding heads, ditching external draft models; on the scheduling side, RadixAttention becomes standard (prefix reuse tech), continuous batching and chunked prefill become standard.

  3. 2025-2026, hardware-software integration. The paradigm shifts to making models inherently inference-friendly from the training stage. Model structures and GPU features are co-designed, attention evolving from MLA (Deepseek-v3’s breakthrough) to NSA (hierarchical sparse matrices); EAGLE-3 (feature-level drafts), MTP (self-speculation, even skipping draft [thinking process])

  4. Quantization using NVFP4 (hardware-supported, performance boosted)

  5. PD separation (costs drop another 30-40%)

Overall, large model evolution tech ties closely to actual work divisions in big companies—any problem can be tackled by categorizing, layering, and prioritizing. Some performance waste? Just iteratively refine it, and you’ll squeeze out the cost-performance ratio.

  1. How has the architecture of KV Cache optimization evolved?
  • Under standard MHA, KV grows linearly with sequence length x layers x heads, and at 128K context it starts exceeding weight VRAM. That’s a big problem.

  • Architecture layer: many people try to shrink parameters, compress cache at the source, MQA -> GQA -> MLA -> NSA -> hybrid SSM route. Just make it not so damn sparse (currently in the industry, model activation is usually only 5%-7%, a lot of sparse matrix parameters are wasted).

  • System layer - careful memory budgeting, pagedattention -> prefix/radix -> continuous batching -> chunked prefill -> offload/mooncake. Earlier we mentioned that under memory + sparsity there will be a lot of fragments, right? So treat VRAM as virtual memory paging. pagedattention solves fragmentation, then cross-request reuse (radixattention prefix tree, yes, the version of the red-black tree you’re familiar with), then optimize batching (continuous batching, reusing the same requests as much as possible) -> then balance prefill/decode (chunked) -> finally overflow cache to CPU/NVMe or split into two stages, from the ‘no waste’ principle to ‘reusable’ to ‘can overflow/decouple, can increase concurrency’.

  • Token-level - patching afterwards. H20 -> streamingLLM -> snapKV -> pyramid/DuoAttn -> Ada-KV.

  • Quantization. Precision compression, from FP8/int8 to KIVI 2bit to KVquant 3bit to GEAR/Atom.

  • Retrieval/sparsity: quest/infllm -> Minference -> NSA native sparse, load on demand (yes, it’s the ‘lazy loading’ concept commonly used in frontend, some infrequently used things don’t need ‘preloading’).

  • Merging: MiniCache / KVsharer -> Cam/D2O. Similar content doesn’t need to be stored multiple times in KV, only indexes.

  1. How has large model distillation technology evolved? What does the latest look like now?
  • 2015, one-hot was popular, the father of reinforcement learning said directly memorizing answers is too wasteful (BERT was also popular then, easy to overfit), and proposed that the essence of distillation is that large models should learn the thinking, not the answer. This is the ‘root cause’ of all technological development.

  • 2016-2019, SeqKD proposed whole-sentence distillation, DistilBert proposed compression (retaining 97% capability).

  • 2024, the LLM era exposed distribution mismatch (emergence). When distilling autoregressive large models, old methods collapsed. Students learn teacher outputs during training, but generate their own outputs during inference, so errors accumulate.

  • 2024-2025, three adjustable knobs (Forward KL [safe but mediocre] -> Reverse KL (inverse reinforcement learning, sharp but prone to collapse) -> JSD -> Skew KL (DistiLLM adaptive), just tuning parameters, utterly useless, a year wasted on trial and error.

  • 2024, engineering compression. Retraining is still expensive, first structurally prune, then continue training with distillation, reducing training cost. (Large models distill data, used as data source to retrain small models)

  • 2025, paradigm shift, from distribution to reasoning process learning (learning of thinking’s thinking). This is the most powerful step. R1 generates 800k CoT reasoning chains, fed to small models (1.5B-80B) via SFT, and small models achieve o1-mini level reasoning at 1/20 the cost. The distillation target upgrades from output distribution (weights) to (learning your learning method [thinking process, which foreigners hype as meta-learning]), and concurrently SPIN proves even a classroom is unnecessary—self-play / left-right hand combat (self-play self-improvement).

  • De-white-boxing: black-box / teacher-free emerges in parallel. White-box obtaining logits is limited by architecture, while the black-box route (synthetic data SFT, PAD preference-aligned distillation) and teacher-free (SPIN) free distillation from dependence on teacher internals, moving toward “strong models generate data, weak models learn behavior” (that is, learning QA, problem-solving thought processes, and the thinking that produces those thought processes together).

  • 2015, one-hot was popular, the father of reinforcement learning said directly memorizing answers is too wasteful (BERT was also popular then, easy to overfit), and proposed that the essence of distillation is that large models should learn thinking, not answers. This is the ‘root cause’ of all technological development — at that time there was a bible in the RL field called “The Bitter Lesson”, which said don’t manually label, just throw everything before labeling to the large model and let it learn and reflect by itself.

Similar Articles

@ZeroZ_JQ: https://x.com/ZeroZ_JQ/status/2079504278922891568

X AI KOLs Timeline

This article provides an in-depth explanation of the principle of reasoning effort in large language models: by adjusting the reasoning effort level (low/medium/high) on the same model, more intermediate reasoning trajectories (serial autoregressive computation) are allowed before outputting the final answer, thereby making trade-offs among answer quality, response speed, and computational cost. The key is that the model has learned to organize longer generation processes into effective computation, rather than simply increasing parameters or network layers.

@NFTCPS: You keep talking about AI, but can't even explain what a Transformer is? There's a repo that goes all out — builds a GPT from scratch without using any high-level libraries. It lays out exactly how Attention, Multi-Head, Feed-Forward, Embedding, Residual connections, and Layer Norm are pieced together. And it's not just the model; the entire pipeline is covered…

X AI KOLs Timeline

A GitHub open-source project that implements the complete GPT training pipeline from scratch, including data preprocessing, pretraining, SFT, and RLHF post-training, all based on native PyTorch. Ideal for developers who want to deeply understand the Transformer architecture.

@tanzhengmc97: https://x.com/tanzhengmc97/status/2066531753762656730

X AI KOLs Timeline

Explained the operating principles of large models in easy-to-understand language, including word vectors, Transformer attention mechanism, next-word prediction training, and emergent abilities, suitable for beginners to understand basic AI concepts.

@snowboat84: Continuing the discussion on applying physical models in AI. Today's Transformer uses attention to allow information at different positions in a sequence to interact, but this mixing is very likely lossy and irreversible. Independent pieces of information get blurred and lost as they mix, and it's impossible to precisely reverse-engineer the input from the output. What we want is a different kind of interaction...

X AI KOLs Timeline

The author discusses the problem of information loss and irreversibility caused by the Transformer's attention mechanism, and proposes drawing inspiration from the physical model of soliton propagation to design a reversible, zero-loss interaction layer as a direction for improving existing AI model architectures.