The TWIML AI Podcast
The TWIML AI Podcast

Dataflow Computing for AI Inference with Kunle Olukotun - #751

In this episode, we're joined by Kunle Olukotun, professor of electrical engineering and computer science at Stanford University and co-founder and chief technologist at Sambanova Systems, to discuss reconfigurable dataflow architectures for AI inference. Kunle explains the core idea of buildin

Featured Speakers

Kunle Olukotun Guest

Topics Discussed

Episode Summary

Executive Summary: Kunle Olukotun explains SambaNova’s reconfigurable dataflow architecture and why it fits modern AI inference: models are mapped as graphs onto hardware to minimize memory traffic, maximize utilization, and support low-latency, multi-model, agentic workloads. The conversation also covers compiler mapping, dynamic reconfiguration research, and the performance/efficiency gains versus GPUs.

Main Topics: Reconfigurable dataflow architecture (Priority: 5/5): Olukotun defines the core idea: represent ML computation as a dataflow graph and configure hardware to match that graph, avoiding instruction-by-instruction execution. Why LLM inference fits the architecture (Priority: 5/5): The discussion explains that inference is memory-bandwidth-bound, so SambaNova’s design reduces unnecessary data movement and fuses larger portions of the model to improve efficiency. Hardware organization and memory hierarchy (Priority: 4/5): The SN40L chip and RDU-based system use multiple memory tiers and chip-to-chip interconnects to keep data local and sustain high utilization across large models. Compiler and model mapping workflow (Priority: 4/5): They detail how PyTorch graphs are compiled into operators, tiled, parallelized, and sharded across RDUs, with custom kernels possible in Python rather than CUDA. Inference, batching, and model switching performance (Priority: 5/5): The architecture is positioned as delivering superior tokens/sec, latency, and high-throughput behavior while preserving low latency under batching and enabling rapid model switching. Agentic AI and orchestration support (Priority: 4/5): The episode explores agentic systems, caching of plans, multi-model orchestration frameworks, and the need for low-latency switching among specialized models. Future research: dynamic reconfigurable dataflow (Priority: 3/5): Olukotun describes newer work on making dataflow architectures more dynamic, with the STEP intermediate representation and future hardware/software co-design for changing graphs and tensor shapes.

Key Arguments: AI algorithms are naturally expressed as dataflow graphs, so hardware should be built to execute those graphs directly rather than fetch instructions every cycle. Reconfigurability matters because different models and graphs require different hardware configurations, and configuration can happen on microsecond timescales. Reconfigurable dataflow removes shared-memory synchronization overhead; communication is handled with tokens/dataflow tags rather than locks and barriers. LLM inference is fundamentally constrained by HBM bandwidth, so reducing data movement is the main lever for performance and energy efficiency. SambaNova fuses entire decoders, not just attention blocks, yielding broader bandwidth savings than techniques like flash attention alone. The system keeps critical resources busy asynchronously, achieving much higher utilization than GPUs and overlapping compute, memory access, and interconnect communication. Model mapping is handled through compiler transformations such as tiling, parallelization, and sharding, starting from PyTorch graphs. The platform can host multiple models simultaneously and switch among them in about a millisecond, which is valuable for multi-tenant and agentic deployments. Agentic workflows benefit from caching plans and from orchestration frameworks that coordinate multiple specialized models. Dynamic reconfigurable dataflow is the next step: retain efficiency in the static case while allowing portions of the system to change at runtime with low overhead.

Data Points: SN40L transistor count: 100 billion - Current SambaNova chip discussed as the production system Process node: 5-nanometer - SN40L chip manufacturing detail On-chip memory: 0.5 GB - First tier of the SN40L memory hierarchy HBM capacity: 64 GB - High-bandwidth memory connected to the accelerator DDR capacity: 1.5 TB - High-capacity memory tier on the system LLM example model size: 8 billion parameters - Llama 3.1 8B used to explain decoder mapping Decoder count in example model: 32 decoders - Used to illustrate mapping the model across RDUs Model fitting capacity: Up to 5 trillion parameters total - Total model capacity supported in high-capacity memory Model switch latency: About 1 millisecond - Switching between models on the system Reconfiguration time: On the order of microseconds - Time to reconfigure the dataflow hardware Utilization gain: 2 to 3 times higher - Fraction of busy time on RDU compared with GPUs Latency advantage at high throughput: About 5x better - SN40L-based system versus GPUs at very high batch sizes Low-latency speedup: 10x or faster - Matrix-vector style communication/computation compared with GPUs Performance-per-watt improvement: 5 to 10x - Projected combined benefit for future agentic workloads Implementation time for DeepSeek variant: About 1 week - Time to get DeepSeek’s multi-headed latent attention running on the system Agentic compiler-system gain: 3.5 to 4x better - Adaptive self-improvement loop versus using an LLM out of the box

Pivotal Quotes: "We have a data flow problem, right? So let's build a data flow computer, right?" — Kunle Olukotun: Core thesis for building hardware that directly matches ML computation graphs "Reconfigurable DataFlow has none of that, right?" — Kunle Olukotun: He is contrasting the architecture with shared-memory parallel systems that rely on locks and barriers "You don't move any data that you shouldn't have to across the HBM bandwidth." — Kunle Olukotun: Explaining the key optimization principle behind SambaNova inference performance

Implications: The episode suggests AI infrastructure will increasingly be specialized around data movement, model switching, and orchestration rather than raw FLOPS. For builders, this points to hardware/software co-design, compiler automation, and agent-friendly systems as the next major performance frontier.

🔓 Sign Up for Unlimited Episode Search

About The TWIML AI Podcast

View all episodes from The TWIML AI Podcast