Systems Papers

Systems paper note는 infrastructure, training efficiency, inference serving, distributed execution, agent tooling, reproducibility를 다룹니다.

Some systems-heavy papers are kept in Architecture Papers when the contribution changes a core model primitive. Use this section as a bridge rather than duplicating the note.

PaperWhy it matters for systems
FlashAttentionexact attention with lower HBM traffic and activation memory
GShardsparse MoE architecture whose claims depend on automatic sharding, compiler partitioning, and distributed execution

Reading Axes

  • What bottleneck is addressed: memory, compute, communication, I/O, latency, or reliability?
  • What is the system boundary: kernel, runtime, framework, scheduler, serving stack, or workflow?
  • What workload is evaluated?
  • Are baselines and hardware assumptions stated clearly?
  • Can the result be generalized beyond the reported setup?
  • Is the claim about latency, throughput, memory, cost, reliability, or developer workflow?

Concepts

0 items under this folder.