Skip to main content
Latent Space

NVIDIA's AI Engineers: Agent Inference at Planetary Scale and "Speed of Light" — Nader Khalil (Brev), Kyle Kranen (Dynamo)

83 min episode · 3 min read
·
Nader Khalil,Kyle Kranen

Episode

83 min

Read time

3 min

Topics

Productivity, Remote Work, Startups

AI-Generated Summary

Key Takeaways

  • Agent Security Constraint: Agents capable of three actions — file access, internet access, and code execution — should only ever be granted two simultaneously. Combining file access with internet access risks malware injection; combining code execution with internet access creates uncontrolled vulnerability surfaces. Enforcing this two-of-three rule at the infrastructure level is the practical starting point for securing agentic deployments in enterprise environments today.
  • Prefill-Decode Disaggregation: Separating prefill (compute-bound, quadratic scaling) from decode (memory-bound, linear scaling) into distinct hardware pools eliminates step-synchronous scheduling bottlenecks and allows independent scaling of each phase. Dynamo implements this via a Kubernetes component called Grove, which dynamically adjusts the ratio of prefill to decode workers as workload characteristics shift, delivering measurable throughput gains over single-engine inference deployments.
  • KV Cache Efficiency via MLA: DeepSeek's Multi-Head Latent Attention compresses KV cache so aggressively that a 128,000-token context fits into roughly 8 gigabytes, compared to 40–80 gigabytes for a similarly sized LLaMA model at equivalent precision. Architects evaluating long-context serving should prioritize MLA-style attention mechanisms as a concrete architectural lever before scaling hardware, since the memory reduction directly lowers per-token cost.
  • SOL (Speed of Light) Framework: NVIDIA uses "SOL" as a first-principles forcing function: establish the theoretical maximum performance before layering in operational constraints. The process starts by asking what physics allows, then works backward to identify what is blocking that limit. Applied to software delivery, SOL surfaces the minimum viable path to a milestone and prevents teams from accepting artificial timelines without understanding root causes.
  • Wide Expert Parallelism at Scale: For Mixture-of-Experts models, an optimization called Wide EP requires a parallelism degree of 32, exceeding the 8-GPU NVLink domain of H100 systems and necessitating the NVL72 GB200 interconnect fabric. Running DeepSeek-class MOE models on this configuration yields approximately 35x lower per-token cost compared to Hopper-based deployments, making interconnect topology a primary cost variable when sizing inference infrastructure for large sparse models.

What It Covers

Nader Khalil (Brev/NVIDIA) and Kyle Kranen (Dynamo/NVIDIA) cover the acquisition of Brev by NVIDIA, the architecture of Dynamo's data center-scale inference engine, prefill-decode disaggregation, KV cache optimization, agent security constraints, and the trajectory of long-running autonomous agents in production environments.

Key Questions Answered

  • Agent Security Constraint: Agents capable of three actions — file access, internet access, and code execution — should only ever be granted two simultaneously. Combining file access with internet access risks malware injection; combining code execution with internet access creates uncontrolled vulnerability surfaces. Enforcing this two-of-three rule at the infrastructure level is the practical starting point for securing agentic deployments in enterprise environments today.
  • Prefill-Decode Disaggregation: Separating prefill (compute-bound, quadratic scaling) from decode (memory-bound, linear scaling) into distinct hardware pools eliminates step-synchronous scheduling bottlenecks and allows independent scaling of each phase. Dynamo implements this via a Kubernetes component called Grove, which dynamically adjusts the ratio of prefill to decode workers as workload characteristics shift, delivering measurable throughput gains over single-engine inference deployments.
  • KV Cache Efficiency via MLA: DeepSeek's Multi-Head Latent Attention compresses KV cache so aggressively that a 128,000-token context fits into roughly 8 gigabytes, compared to 40–80 gigabytes for a similarly sized LLaMA model at equivalent precision. Architects evaluating long-context serving should prioritize MLA-style attention mechanisms as a concrete architectural lever before scaling hardware, since the memory reduction directly lowers per-token cost.
  • SOL (Speed of Light) Framework: NVIDIA uses "SOL" as a first-principles forcing function: establish the theoretical maximum performance before layering in operational constraints. The process starts by asking what physics allows, then works backward to identify what is blocking that limit. Applied to software delivery, SOL surfaces the minimum viable path to a milestone and prevents teams from accepting artificial timelines without understanding root causes.
  • Wide Expert Parallelism at Scale: For Mixture-of-Experts models, an optimization called Wide EP requires a parallelism degree of 32, exceeding the 8-GPU NVLink domain of H100 systems and necessitating the NVL72 GB200 interconnect fabric. Running DeepSeek-class MOE models on this configuration yields approximately 35x lower per-token cost compared to Hopper-based deployments, making interconnect topology a primary cost variable when sizing inference infrastructure for large sparse models.
  • CLI-First Agent Tooling: Exposing business application functionality through CLIs rather than arbitrary API calls provides agents with a predefined, auditable action space — reducing security surface area and leveraging the large volume of command-line data present in LLM pretraining corpora. NVIDIA internally built CLIs for Outlook and Slack, then open-sourced the pattern. Teams building agentic workflows should prioritize CLI wrappers over freeform API access for any tool handling sensitive organizational data.

Notable Moment

Kyle describes a theoretical inference architecture where prefill operates locally on document chunks while decode runs globally across the full sequence. This design would eliminate the quadratic scaling problem in prefill entirely by processing independent document segments in parallel — a structural change that no published model currently implements but that could unlock context lengths well beyond today's one-million-token ceiling.

Know someone who'd find this useful?

Episode Transcript

Agents can do three things. They can access your files. They can access the Internet, and then now they can write custom code and execute it. You should really only let an agent do two of those three things. If you can access your files and you can write custom code, you don't want Internet access because that's one c, vulnerability. Right? If you have access to Internet and your file system, you should know the full scope of what that agent's capable of doing. Otherwise, malware can get injected or something that can happen. And so that's a lot of what we've been thinking about is, like, you know, how do we both enable this because it's clearly the future, but then also, you know, what what are these enforcement points that we can start to, like, protect? Alright. Welcome to the latest podcast in the Chroma studio. Welcome to all the guests here. We're back with our guest host, Vibhu. Welcome. Good to have you back. And our friends, Netter and Kyle from NVIDIA. Welcome. Yeah. Thanks for having us. Yeah. Thank you. Actually, I don't even know your titles. I know you're, like, architect something of Dynamo. Yeah. I I'm one of the engineering leaders and arch architects of Dynamo. And you're director of something developers. Yeah. You're the developer's developer's developer's guy at NVIDIA. Source, agent marketing, Brev, and, like, dev tools and stuff. Yeah. I'm the focus. And we're we're kind of recording this ahead of NVIDIA GTC, which is coming to town, again, or taking over town, which, which we'll all be at. And we'll talk a little bit about your sessions and stuff. Yeah. Yeah. Yeah. We're super excited for it. One of my favorite memories for Nader, like, you always do, like, marketing stunts. And, like, while you were rev, you, like, had this surfboard that you, like, went down to GTC with. And, like, Nvidia apparently liked you so much that they bought you. Like, what what what was that like? Yeah. Yeah. We we, our logo was a shocker. We we, we were always just kind of, like, trying to keep true to who we were. I think, you know, so much of startups, you're, like, trying to pretend that you're a bigger, more mature company than you are. And it was actually Evan Conrad, SF Compute, who was just like, you guys are guest. Yeah. Yeah. Oh, really? Yeah. Amazing. Yeah. He was just like, guys, you're two dudes in the room. Why are you pretending that you're not? And so then we were like, okay. Let's make the logo of Shaka. We brought surfboards to our booth to GTC, and the energy was great. Some palm trees too. They they actually poked out over, like, the the walls. So you can you could see the bread booth so funny. And no one else did. Just from very far away. Oh, so you remember it back then? I I …

Get the full transcript (19,298 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Latent Space transcripts →

You just read a 3-minute summary of a 80-minute episode.

Get Latent Space summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links. As an Amazon Associate, SignalCast earns from qualifying purchases.

Tools

  • by NVIDIA

    Dynamo implements this via a Kubernetes component called Grove, which dynamically adjusts the ratio of prefill to decode workers as workload characteristics shift, delivering measurable throughput gains over single-engine inference deployments.

Gear

  • by NVIDIA

    For Mixture-of-Experts models, an optimization called Wide EP requires a parallelism degree of 32, exceeding the 8-GPU NVLink domain of H100 systems and necessitating the NVL72 GB200 interconnect fabric.
  • by NVIDIA

    For Mixture-of-Experts models, an optimization called Wide EP requires a parallelism degree of 32, exceeding the 8-GPU NVLink domain of H100 systems and necessitating the NVL72 GB200 interconnect fabric.

More from Latent Space

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best AI Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Startups & Product Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Latent Space.

Every Monday, we deliver AI summaries of the latest episodes from Latent Space and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime