
Tech Threads: Weaving the Intelligent Future
Jun 16, 2026 · 39 min · 12 segments
In this episode of Tech Threads: Weaving the Intelligent Future, Baya Systems’ Nandan Nayampally sits down with Charlie Cheng, founder and CEO of TC Lab, for an in-depth conversation on the memory…
Charlie ChengGuest
Nandan NayampallyHostAnd it went from a physics problem or a pure technology problem to substantially faster a business problem.

And because of the diversity, compute and memory are relatively balanced, and they're both sort of new frontiers that everyone is exploring.

But I think something really changed in 2025 when people start to really deploy inference as a workload for productivity gains.

And that's really where we want We want to see AI to be productive in our everyday use.

And in the inference, everyone is using, relatively speaking, exactly the same computational algorithm and model.

And in Decode, specifically, for every token generated, we have to run through the model with all the contacts, KVCache, one token at a time.

And that's when you really see memory and specifically memory bandwidth being the constraint.

It essentially establishes the roofline at which you as a compute platform cannot move faster than the roofline.
Yeah, I think that's probably a... a fair kind of assessment of what has happened, right? The memory wall has kind of exploded.
And I think before we go to your answer to this, can you set up a stage for those that are not chip architects? I think you've partially answered that question.
When a large AI model is running generating tokens in real time, where is the actual bottleneck? And why is the memory bandwidth binding? I think you've touched on that.
If you could dive a little bit deeper, I think that'll be much appreciated.

So when inference jobs are running, the first part of it called pre-fill is when you take the input, the prompt, or the document, whatever you start with, and you try to build context.
And it went from a physics problem or a pure technology problem to substantially faster a business problem.

And because of the diversity, compute and memory are relatively balanced, and they're both sort of new frontiers that everyone is exploring.

But I think something really changed in 2025 when people start to really deploy inference as a workload for productivity gains.

And that's really where we want We want to see AI to be productive in our everyday use.

And in the inference, everyone is using, relatively speaking, exactly the same computational algorithm and model.

And in Decode, specifically, for every token generated, we have to run through the model with all the contacts, KVCache, one token at a time.

And that's when you really see memory and specifically memory bandwidth being the constraint.

It essentially establishes the roofline at which you as a compute platform cannot move faster than the roofline.
Yeah, I think that's probably a... a fair kind of assessment of what has happened, right? The memory wall has kind of exploded.
And I think before we go to your answer to this, can you set up a stage for those that are not chip architects? I think you've partially answered that question.
When a large AI model is running generating tokens in real time, where is the actual bottleneck? And why is the memory bandwidth binding? I think you've touched on that.
If you could dive a little bit deeper, I think that'll be much appreciated.

So when inference jobs are running, the first part of it called pre-fill is when you take the input, the prompt, or the document, whatever you start with, and you try to build context.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.