Well, S3 can have a lot of namespaces.

嗯，S3可以拥有众多命。

And then we're also going to pass through the Google namespace.

然后我们还将通过 Google 命。

As you query the namespace more, Turbo Puffer gets faster.

随着你对命的查询增多，Turbo Puffer 的响应速度快。

And that way we are only constrained in our scalability on how many namespaces S3 can have.

这样一，我们的扩展性仅受限于S3能容纳多少个命。

And just like how we've done previously, we're going to tap into the Google Maps namespace.

就像我们之前所做的样，我们将利用 Google 地图命。

And this is where the Google namespace comes into play.

这就是 Google 命发挥作用的地方。

And we'll go into the same google.maps.controlposition namespace.

我们将进入相同的 google.maps.controlposition 命。

What we see our customers do is generally export the namespace locally and then try to visualize it.

我们观察到客户通常的做法是先将命导出到本地，然后尝试进行可视化处理。

And this is in the google.maps.controlposition namespace.

这是在 google.maps.controlposition 命中。

Cause I mean, I was like 40 million, 40 million namespaces.

因为我的意思是，我就像有4000万个，4000万个命。

In Turbo Puffer, a namespace maps directly to one shard.

在Turbo Puffer中，一个命直接对应一个分片。

I'm aware that namespacing is a part of TurboPuffer and scaling that has, I believe it's like 14 million namespaces or something.

我了解到命是TurboPuffer扩展的一部分， 据我所知，它已经达到了约1400万个命或类似的规模。

There's still a lot of rules around how you turn things on and filter them or, you know, like namespace, different logging and stuff.

仍然有很多规则围绕着如何开启某些功能和过滤它们，或者像命、不同的日志记录等内容。

The reason you'd want crypto is because the representation of the namespace that we're talking about, the ID space that everybody's in, we'd want modifying and editing and updating that namespace to be done in a censorship resistant way.

你想要加密货币的原因是， 我们所谈论的命，也就是每个人所在的ID， 我们需要以一种抗审查的方式进行修改、编辑和更新这个命。