CharlieKey takeaways from your favorite podcasts
← 6 October 2026Training Data

Google's Head of AI Infra, Amin Vahdat, on the Architecture of Intelligence

Amin Vahdat argues that AI infrastructure is won by co-designing chips, models, networks, buildings and power around delivered workload performance, where specialization pays only if the workload is durable and large.

Watch on YouTube ↗

Word for word

There is this opportunity where the more you specialize to a particular workload the less flexible it is the faster the more power efficient the hardware is going to be.
If you become fully funible. If you become fully flexible to anybody's hardware, software, network, storage, compute, etc. stack. So the case for code designing is between each one of those layers there's a big impedance mismatch if you try to get full generality. And so there might be 10% 20% 2x across each of these layers. You start multiplying those optimization opportunities through and all of a sudden you're left with a big endto-end opportunity in terms of whatever you want to say intelligence per watt or goodput per watt that you can leverage even again all the way down to power delivery and power availability software optimizations etc. So pros are you can run anywhere anytime you have no lock in. Cons are you're leaving significant and in all likelihood significant amount of performance on the table.
What's your flop's utilization. So for example for a particular workload if you have in theory teraflop or a pedlop capable for your workload what fraction of that are you delivering?

Do more with Charlie

Free — sign in with your email, no password.