Sundar PichaiGuest
Elad GilHostAs I think about the AI race in 2026, one thing that strikes me is Google has for so long had speed as the place it tries to differentiate.
And so original Google search was really fast and famously displayed the search query time within the results sort of showing off.
And I'm curious how much this is part of the explicit product strategy and how you think of it, or it's much more nuanced than that.

Let's call it as latency for this purpose, right? And as like one of the distinguishing features of a great product.

And also almost always reflects the technical underpinnings of the product having been done well.

There's a different speed which matters too, which is the speed of shipping and iteration and release cycles.

So there's some sense of how do you balance that? So that's where it gets more complicated.

But to give an example like search, you know, I was speaking with the teams, right? Like they now have for sub teams, like latency budgets,

You'll get 50% credit if, so if you ship something which, you know, shaves off three milliseconds, you earn 1.5 milliseconds for your latency budget and 1.5 milliseconds gets passed on to the user, right? And depending on what we think you're doing, some people may get a latency budget of 30 milliseconds or 10 milliseconds.

And for context, I guess humans pick it up in the low hundreds of milliseconds, is that correct, in terms of where it actually impacts? That's right, yeah,

I think we've actually, last I checked the dashboards and the metrics, we've actually improved search latency by 30% in the last five years.
As I think about the AI race in 2026, one thing that strikes me is Google has for so long had speed as the place it tries to differentiate.
And so original Google search was really fast and famously displayed the search query time within the results sort of showing off.
And I'm curious how much this is part of the explicit product strategy and how you think of it, or it's much more nuanced than that.

Let's call it as latency for this purpose, right? And as like one of the distinguishing features of a great product.

And also almost always reflects the technical underpinnings of the product having been done well.

There's a different speed which matters too, which is the speed of shipping and iteration and release cycles.

So there's some sense of how do you balance that? So that's where it gets more complicated.

But to give an example like search, you know, I was speaking with the teams, right? Like they now have for sub teams, like latency budgets,

You'll get 50% credit if, so if you ship something which, you know, shaves off three milliseconds, you earn 1.5 milliseconds for your latency budget and 1.5 milliseconds gets passed on to the user, right? And depending on what we think you're doing, some people may get a latency budget of 30 milliseconds or 10 milliseconds.

And for context, I guess humans pick it up in the low hundreds of milliseconds, is that correct, in terms of where it actually impacts? That's right, yeah,

I think we've actually, last I checked the dashboards and the metrics, we've actually improved search latency by 30% in the last five years.
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.