Output-Stationary Dataflow: Interview Drills

Interview drills

Interview Drills for Output-Stationary Dataflow is anchored on Partial-sum spill rate and accumulator energy per output element across matrix and convolution workloads.. Convert measurements into mechanism-backed decisions with clear owner accountability.

PROMPT
You observe regression in Partial-sum spill rate and accumulator energy per output element across matrix and convolution workloads. for Output-Stationary Dataflow. Explain root cause and release decision.

STRONG ANSWER
1. Defines workload and first failing mechanism.
2. Explains mechanism: Output-stationary dataflow keeps partial sums local in each PE accumulator until an output tile is fully reduced, minimizing partial-sum writeback/readback traffic. Activations and weights move through the array while each PE repeatedly accumulates contributions for its assigned output coordinate, then emits the final result once complete. This can materially reduce memory energy when reduction depth is high, but requires accumulator sizing, precision management, and overflow controls that match workload statistics. If reductions exceed local capacity or pipeline timing is misaligned, frequent spills to buffer hierarchy erase the intended efficiency gains.
3. Requests proving artifact: Accumulator sizing and spill analysis with precision budget and writeback frequency breakdown.
4. Proposes bounded fix + owner + rollback-safe validation.

WEAK ANSWER
Gives generic optimization ideas without mechanism proof or ownership.

AI accelerator deep dive

Systolic efficiency is governed by feed quality, tile fit, and bubble control.

Concept diagram

SYSTOLIC WAVEFLOW

operand stream -> wavefront launch -> PE mesh compute -> reduction/writeback
                         ^ bubbles and feed stalls reduce realized throughput

Metric graph

UTILIZATION LOSSES

tile mismatch      ███████
feed stalls        █████████
sync bubbles       █████

Metrics and artifacts to collect

• mesh occupancy timeline

• fill-drain overhead

• tile mismatch histogram

• DRAM stall attribution

Mini case study

Increasing mesh size did not help until scheduling and tile alignment removed persistent wavefront bubbles.

Debug branches

• Measure bubble source first

• Classify compute vs memory starvation

• Tune tile policy before frequency changes

Senior review question

Ask: which first-principles bottleneck class explains the symptom, and what artifact proves it reproducibly?

Key takeaways

• Tie every accelerator claim to a reproducible workload slice and one primary metric trend.

• Prefer bounded fixes with clear owner and rollback boundary over broad tuning bundles.

Common pitfalls

• Optimizing synthetic kernels without production-shape validation.

• Reading average latency while ignoring p95 and p99 behavior.

• Declaring sparse or precision wins without fallback and quality evidence.

Interview answer expansion

A strong answer on Output-Stationary Dataflow names the workload symptom, explains mechanism (Output-stationary dataflow keeps partial sums local in each PE accumulator until an output tile is fully reduced, minimizing partial-sum writeback/readback traffic. Activations and weights move through the array while each PE repeatedly accumulates contributions for its assigned output coordinate, then emits the final result once complete. This can materially reduce memory energy when reduction depth is high, but requires accumulator sizing, precision management, and overflow controls that match workload statistics. If reductions exceed local capacity or pipeline timing is misaligned, frequent spills to buffer hierarchy erase the intended efficiency gains.), and proposes one measurable validation plan.

Then it identifies owner and fallback action if the proposed fix under-delivers.

The goal is practical engineering reasoning, not keyword listing.