Megakernels dissected: launch overhead, rare compute overlap, and lots of barrier waiting

simran_s_arora · x · 2026-11-17

Dylan Lim's thread dissects what megakernels actually deliver: fusing a whole model into one kernel forces all ops to share the same resources, which is suboptimal for modern architectures — e.g. KimiK3's KDA and MLA instructions each perform best at different ctagroup modes, and PTX forbids mixing them in one kernel, so a megakernel can't run both at their best structure.

Many megakernel benefits turn out to be over-engineered: launch overhead equals intra-kernel grid synchronization, compute overlap is rare, and paged memory preloading accounts for only 3% of the Llama 1B end-to-end result. The 'What's advertised vs Reality' kernel-timeline chart shows much of real-world time spent 'waiting on a barrier'.

Original post →

More from Infra

Infra channel →