Skip to main content
Search

# ReplaySSM

2 related articles

Subscribe to updates
  1. arXiv

    SSM decoding stops writing state every step: caching recent inputs halves state traffic and matches vLLM speculation

    State-space model decoding previously read and wrote the full recurrent state at every step, making state traffic the memory-bandwidth bottleneck and leaving speculative decoding without cheap rollback. ReplaySSM represents the state as a checkpoint plus a buffer of recent inputs, writes the checkpoint only when the buffer fills, and computes outputs directly on most steps. Implemented in vLLM for Mamba-2 and Gated DeltaNet, it speeds up standard decoding over a tuned baseline at serving batch size 256, reaches about the throughput of vLLM's speculative decoding on two 120B-class models, and separate state precisions reduce output KL divergence and downstream accuracy losses.

  2. Hybrid-model decoding has a new bottleneck: stop writing the SSM state every step, and speculative throughput reaches 2.10x

    Hybrid models interleave state-space layers with a few attention layers, and the state-space layers use a fixed-size state instead of a key-value cache that grows with context, yet at serving batch sizes they become the latency bottleneck and complicate speculative decoding and quantization. ReplaySSM represents the state as a checkpoint plus a buffer of recent inputs, separating output computation from state updates so most steps append inputs without writing state back. Across four hybrid models, the kernel runs 1.46x to 1.80x faster and the decode step 1.20x to 1.47x faster at batch size 256, and two 120B-class models reach 1.85x and 2.10x the speculative decoding throughput of vLLM at batch size 512.

You’re all caught up