嘉宾访谈·中文精读

纳文·拉奥:4D 计算、AI 的能源墙与超越生物学

Naveen Rao: 4D Computing, AI's Energy Wall & Beating Biology

纳文·拉奥谈能源是否真是瓶颈、token 成本与电力合同,去除抽象层、动力系统与新机器,以及产品化与移植现有模型。

官方音频00:00 / --:--

本期章节点时间可跳到音频对应位置

  1. 0:00欢迎纳文·拉奥
  2. 4:45能源真的是问题吗?单个 token 的成本、电力合同与待填补的缺口
  3. 10:24去掉中间商:抽象层、动力系统与一种新型机器
  4. 19:46查马斯加入:通往产品的路径、移植现有模型与组建团队
中文精读由 AI 基于原始节目改写,非官方翻译,可能存在偏差或错误;观点归属与表述以原音频与官方文稿为准。说明

谷歌每个月要处理 3200 万亿个 token。按每 token 10 焦耳这个偏低的口径算,光是这一家公司的 AI 服务就要吃掉 12 吉瓦电力。

整个美国投进数据中心的电力大约是 40 吉瓦,全球加起来不到 100 吉瓦。一家公司占了全球的十分之一还多。

对照另外两个数字:人脑的功率是 20 瓦,一只松鼠的大脑是 8 毫瓦。

把这三组数字摆在一起的人是纳文·拉奥(Naveen Rao),Unconventional AI 的联合创始人兼 CEO。他之前创过两家公司:2014 年的 Nervana Systems,做 AI 芯片,那个年代还没人把 AI 当回事,后来卖给了英特尔;之后是 MosaicML,做 GPU 平台化,2023 年并入 Databricks,如今贡献了 Databricks 总营收的四分之一。他的履历里有一段别人补不上的东西:读完电气工程,又回头拿了神经科学博士。理由很简单,他想知道怎么造一台会思考的机器。五六岁的时候家里就有电脑了,他说自己当时以为编程是个解谜游戏。

按现在的曲线,三年左右就要撞墙

拉奥说,能源不遥远,是三年内的事。

他的推算很直接:模型越大,能耗越高;需求在涨,能耗也涨。把这两件事画在图上,上面是一条指数增长的市场曲线,2025 年人们已经在说万亿美元市场,2030 年只会更大;下面是一条几乎线性的能源供给曲线。中间裂开的那道缝,就是他这间公司存在的全部理由。

数据中心这几年的瓶颈换过好几轮。最早是地板面积,能不能拿到机柜空间。然后是网络设备。再然后是 GPU。现在是电。顺序整个反过来了:先去签电力合同,再倒推怎么把这份电填满,用 GPU 和网络设备把它变成基础设施。

他还给了一个成本结构:每次你在 ChatGPT 里发一句话,其中大约 50% 的成本是电费,剩下的是硬件折旧和场地。所以今天整个行业的生意经是这样的,签下一份电力合同,然后想办法让每一瓦都赚到钱。

Unconventional AI 的商业计划就是把这句话反过来写:同样一瓦电,我们比现有硬件多赚一千倍。

生物学给出的证据

人脑功率约 20 瓦。恒河猴的大脑只要 1 瓦。你口袋里的手机大概也是 1 瓦。老鼠和蝙蝠在毫瓦级。松鼠的大脑是 8 毫瓦。拉奥说,松鼠在树枝间跳跃的准确率是千次千中,而这样一颗大脑的功耗,你的手机能同时跑一百多颗。

这些数字的意义很直接:智能本身不需要那么多能量,是当前的实现方式需要。

能量到底花在哪了?拉奥给了一个对比。人类大脑皮层,也就是那层皱巴巴的外壳,信息吞吐大约是每秒 160 亿比特,而皮层里有一百三四十亿个神经元。一块高端 GPU 每秒进出内存的数据接近 30 万亿比特,芯片内部可能还要再高一到两个数量级。

合成系统搬运的比特数比大脑多了三个数量级。能耗就是这么来的。

计算机的历史也没帮上忙。机械、模拟、数字,形态换了三轮,但 1945 年的 ENIAC 和今天的机器在结构上几乎一样:外面一块内存,中间一个计算单元,比特来回搬。ENIAC 当年是为了算炮弹弹道造出来的,目标只有一个,比人算得快。今天的计算机还是这么卖的,这台比那台快一倍。能耗效率从来没有进过设计目标。过去靠缩小晶体管带来的效率红利,也就是摩尔定律,现在也基本停了。

拆掉中间商:从半导体物理直接连到神经网络

拉奥的解法听起来像一句口号:把中间商砍掉。

计算机是层层抽象堆出来的。“数字”本身就是对物理世界的抽象,晶体管并没有真正的一和零,中间有大量状态,是人把它工程化成了一和零。抽象堆到最上面,才长出了神经网络和机器学习这类东西。每一层抽象都是有损的,正因为有损才叫抽象。层数越多,离物理越远,浪费越大。

大脑里没有线性代数,没有浮点数运算。是神经元的物理特性本身涌现出了智能。拉奥想做的事,就是找一层对半导体物理的抽象,直接接到神经网络上去。

这个思路在自然界有现成范本。鸟群里的每只鸟只做一件简单的事:看看左边,看看右边,判断旁边那只往哪飞。放在一起就出现了群飞这种涌现行为。蚁群同理。这套理论叫动力学系统(dynamical systems theory),已经有一百年历史,研究的就是简单组件之间的相互作用如何产生复杂的整体行为。

节拍器、UNO 和稀疏性

拉奥举的例子是节拍器。

学过琴的人都知道那东西,左右摆动,滴答滴答。把好几个节拍器放在一块能轻微滚动的木板上,它们会自己同步到完全相同的相位。没有中央控制,全靠木板被每次摆动推挤的那一点点反作用力。放到几百个,一样会同步。

他问的问题是:这样的系统能不能拿来计算?

他们发布了一个叫 UNO 的模型做验证。UNO 是一台图像生成模型,底座是一组振荡器,没用矩阵乘法。团队在仿真环境里跑通,开源了出去,任何人都能复现。这是第一次有人把这类系统规模化训练并拿到有用的输出,生成的图片是能看的。

他们还放了一张状态空间轨迹图。把系统状态定义成所有振荡器的相位,观察它随时间怎么演化,再用输出条件去约束它:要飞机就走出飞机的轨迹,要汽车就走出汽车的轨迹。不同目标对应不同轨迹。

之后几个月,团队在基础理论上又推进了一步。他们发现可以扔掉一部分连接,系统表现反而更好,也更容易训练。

起点是平方级增长的困境。十个元素两两相连是一百条连接,还行。一千个元素两两相连就是一百万条连接,这条路走不通。稀疏性问的是:扔掉一部分连接,还能不能保住整个系统的行为?答案是不仅能扔,扔掉之后更高效、更可扩展、性能还更强,三件事同时拿到。这个结论在仿真系统里成立,在真实物理系统里也成立。拉奥说这是长久以来没人拿到过的东西,卡住的原因在于过去的问题框架不对。

第一台物理动力学计算机,每张图 500 纳焦

接下来讲的东西,拉奥说是第一次公开。

他们的第一台物理动力学计算机已经做出来了。公司今年一月才正式起步,当时连团队都没凑齐,但定下的目标是年内拿出第一台物理原型。6 月 1 日设计定稿送厂流片,芯片现在已经在实验室里,有实测结果。屏幕上放出了这台机器生成的第一批图像。

关键数字是能耗:生成一张图大约 500 纳焦。作为对照,普通 GPU 的量级是毫焦。纳焦是 10 的负九次方,中间差了好几个数量级。原因很直接,这台机器根本不搬运信息。

拉奥给这类机器起名叫 4D 计算。三个维度来自物理堆叠,芯片垂直堆叠加上平面布局;第四个维度是时间,也就是系统的动力学演化。这条路线和 CPU、GPU 完全不同。CPU 到 GPU 是在做并行化,计算和存储越来越细粒度地并行,但都还是冯·诺依曼架构:内存一块,计算一块,数据来回搬。动力学计算机把计算和存储合成同一个东西,没有内存接口,每个计算单元自己就是存储器。

目标是超越生物学

拉奥关心的指标是“每瓦智能”。

这里存在一个热力学上限,任何系统都不可能越过。哺乳动物的大脑离这个上限只差一到两个数量级。而今天的计算系统,离上限大约差 100 亿倍。

公司的判断是,用三年半可以摸到二维光刻工艺的物理极限。再往后的目标写在公司简介里,只有一句话:超越生物学。他预想的场景是计算无处不在,包括十年内出现的新形态机器人。

随之而来的是数据中心形态的变化。从少数几个吉瓦级的大数据中心,变成散布各地的许多小型数据中心。拉奥认为这是好事:更环保、更本地化、更能适配场景。再往后,是几十亿台机器人动态组合起来解决现实问题。

关于市场,他搬出了杰文斯悖论(Jevons paradox):一样东西的底层成本下降,消耗量会超过成本下降的幅度。价格减半,用量涨不止一倍;价格降到千分之一,用量涨不止一千倍。如果这个逻辑成立,他会催生人类历史上最大的市场。

从原型到产品:两年,一整个机架

演讲结束后,查马斯·帕里哈皮蒂亚(Chamath Palihapitiya)上台提问。他先问生态:英伟达在前面讲过了,从流片到封装,这条路要靠一整圈合作伙伴,从这版早期原型走到能放进别人机架里的东西,需要多久?

拉奥的回答是两年内能出完整产品。形态是一整个机架,一套系统。对外表现为一台虚拟机,跑在某个地方的机架上,由他们运维。接口是网络线缆,token 进、token 出,但内部结构和现有计算机完全不同。

查马斯接着问了一个更实际的问题:现有的模型家族和架构,比如 KVCache 那一整套基于抽象堆出来的机制,你们打算怎么兼容?行业又该怎么迁移过来?

拉奥说迁移这件事中间有一条滑尺,一端是“好多少”,另一端是“愿意忍受多麻烦”。他的选择是把“好多少”做到极致,让迁移本身足够诱人。移植是有的,运算层不用动,要动的是模型层。现有模型可以跑,只是迁移过程需要不少算力。

查马斯追问了一个技术细节:像矩阵乘法这种最基本的运算,你们那里存在吗?

它不存在。你可以把它描述成矩阵乘法,但它不是以矩阵乘法的形式实现的。它以随时间变化的行为来实现。你能分析出,它的每一个时间步,本质上就是当前状态矩阵乘以一个转移矩阵。(纳文·拉奥)

理论家和造芯片的人不说话

查马斯问团队构成。拉奥说这里面有理论家,来自已经有百年历史的动力学系统理论圈子;也有真正流片造芯片的工程师。问题是这两拨人平时不交流。公司最难的事情之一,就是让跨度这么大的技能拼在一起,围绕同一件东西协作。

那有没有一个类似 CUDA 的中间层,让上面的人和下面的人能对话?拉奥说他们做了一套 Python 库。谈不上是 CUDA,但算是一门语言,可以表达带有随机行为的时变元件。这就是上下两层之间的接口。

对话结束时,查马斯说了一句:极其大胆。拉奥说:谢谢。

那台机器每张图只要 500 纳焦,这个数字会被反复引用。但拉奥做事的顺序更说明问题:他先问的是内存和计算为什么必须分开,再去问抽象为什么要堆那么多层。

这两件事都能追到历史上。内存和计算分离,是因为 1945 年的目标是算得比人快,省电不在考虑范围内。抽象一层层堆起来,是因为每一层都让工程更好做,代价是每一层都在漏能量。这两件事在过去八十年里没人有动力去动,因为电一直很便宜。现在电不便宜了,问题就得从物理层重新长出来一遍。

至于这条路能不能走通,两年后那台机架有没有人买,是下一个问题。

  • 判断一家 AI 公司的扩张速度,盯电力合同比盯 GPU 采购单更准。瓶颈已经从芯片换到了电,签下多少瓦决定了它能跑多少 token。
  • 如果每瓦智能真的提升三个数量级,价值锚点会从“谁有最多 GPU”转向“谁的每瓦智能最高”。这条曲线可以当成新的筛选指标。
  • 做模型和应用的团队,现在押注具体硬件架构为时过早,但有一条原则可以先想清楚:模型层保持可移植,运算层不要绑死。迁移成本会成为下一轮竞争的变量。
  • 杰文斯悖论是对需求的乐观依据,成本降一个数量级,用量涨更多。但它同时说明,效率提升不会让总能耗下降,只会让消耗场景变多。
  • 选职业方向的话,跨界的稀缺性在变贵。这家公司最大的内部难题落在沟通上:让动力学理论家和芯片工程师说上同一种语言。能同时听懂两边的人,接下来五年会很值钱。
文稿由本站用语音识别模型(Whisper,基于官方发布音频)机器转写,可能有识别错误,没有说话人标注;人名与数字请以音频为准。
(00:00:00) Naveen Rao, co-founder and CEO of Unconventional AI, which is an AI chip startup. Best known for building and selling to deep tech companies. Naveen is kind of definitionally outlier founder. When I came there, we had about a $20 million business and it was, you know, seven or eight hundred million when I left. I don't think you really understand something until you can build it. Just because something is tried does not mean it's wrong. I'm the opposite of an AI doomer. I think AI is the next evolution of humanity. We need innovation on the hardware substrate to actually build true intelligence. Please welcome Naveen Rao. Hey everyone. Great to be here. (00:00:46) You know, switching gears a little bit to AI now, which you may have heard a little bit about. It's super exciting to be at this conference specifically because, as was said in the intro, I'm the opposite of a doomer. I think AI is one of those transformational technologies that humanity's ever created and will enable us to get to that next level of evolution, which I'm here for. And this is sort of the anti-doomer conference. So let's go. So before we get going, I'll tell you a little bit about myself. You know, it's kind of weird. I'm really right where I wanted to be my whole life. This was me at about five or six years old, something like that. We had a computer very early on, so I'll date myself. But this was in 1978 we got a computer. This is probably in the early 80s. (00:01:32) I learned a program when I was a little kid. I just thought it was like a puzzle. You know, learned to... I became an electrical engineer really because I enjoyed sci-fi and always wanted to think about how I could make an intelligent machine. And, you know, then after a career in building computers, I went back to school and got a PhD in neuroscience. And the idea was like, let's go back to that thing. How do we make computers intelligent? And fortunately, the whole world kind of moved in this direction. So, you know, as a technologist, it's sort of the dream right now. A little bit about me from a company entrepreneurship standpoint. Like, I actually founded the first AI chip company called Nirvana Systems. So, this was in 2014. If anyone remembers back then, there was no AI, or at least not in the common vernacular. (00:02:21) And it was really hard to actually convince people that this is important, much less to build hardware around it. Now, you heard from Jensen up here, like the largest company in the world, a hardware company because of AI. So, we were early on. I think I sold the company way too early to Intel. But I started and ran the AI group at Intel. After I was done with that in 2020, I actually started thinking about the next problem, which was, how do we build bigger models, like the large language models we talk about today? And it was about, how do I build the infrastructure to build those models? And so, we started platformizing GPUs and enabling it to scale and making that easy to use for other people. And after ChatGPT happened in 2022, we were kind of the best game in town for people to start building their own models. So, took off really fast. We decided to actually join forces with Databricks. That was in 2023. And (00:03:13) actually, that's a quarter of the total revenue of Databricks today. So, a lot of fun doing that whole thing with Ali and team at Databricks. And now, I want to tell you about unconventional AI, which is rethinking the foundations of how a computer works. So, we're going back to first principles here to really trying to build a new machine. Computers have worked a certain way for a long time. We want to rethink that for the singular purpose of making something very power efficient. And the goal has been within, it was initially within five years to get to 1000x power efficiency. I've actually revised this to three and a half years because things have gone faster than we anticipated. We've actually solved very deep scientific problems quicker because of AI, interestingly enough. So, just a little bit how we organize. We're truly a top to bottom company. We start with theorists. (00:04:02) These are people with math PhDs and theoretical neuroscience, that kind of thing. They come up with concepts that we think would effectively give us more power efficiency from the perspective of moving less information around. And we then translate that into models that do real things, trained on real data and evaluated against real criteria. So, it's kind of the rubber hitting the road of these concepts. Then eventually, we have to actually build something physical. So, these are people who architect a physical circuit, actually design those circuits, model them, and see if it actually works. So, we try to connect this whole stack together. Then eventually, we have to build a system and a board and all that kind of stuff and build a product. So, is energy really a problem? I'm not sure how much everyone in this audience has thought about this, but interestingly enough, (00:04:51) I'll give you some data points here. This is one company. This is just Google. I'm using Google because Google has actually talked about this publicly. Per month, they cross 3.2 quadrillion tokens. It's a crazy number. I never even think in quadrillions, but that's the world we're in today. And if I just take 10 joules per token of energy, this is actually on the lower end of the energy spectrum for models, but let's just take that number and multiply it out. This is 12 gigawatts. The US puts about 40 gigawatts of energy into data centers today, and we're about half of the data center capacity of the world. And so, we're under 100 gigawatts of data center energy in the world today. 12 gigawatts is going into one company just for AI services. So, you can imagine if models get (00:05:39) bigger, that energy goes up. And if demand grows, which it is, that energy goes up. So, we're going to run out of energy pretty fast. In like three years or so is my estimate. So, really just putting it graphically, this is what we have. We have this huge market that's growing exponentially. Call it a trillion dollar market in 2030. Maybe it's bigger than that. And then we have this kind of linearized energy at the bottom. And so, you've heard a lot about this today, but this gap is the problem. And we want to solve that gap with technology. So, I don't know if people are aware of this, but the way we think about data centers has shifted over the last several years. It used to be about floor space. Can I get the floor space? Can I get the rack space? Then it was about networking equipment. Then it became (00:06:25) about GPUs. Today, it's about energy. First, you think about energy. I get the energy contract, and then I have to figure out how to fill it and basically create infrastructure out of GPUs and things like this. About 50% of the cost of serving a token, so every time you try something on ChatGPT, 50% of that cost is energy. The rest of it is the capex of the hardware and the floor space and all that kind of stuff. So, today, we sort of think about it as, I get a power contract, and I need to monetize every watt. And simply put, our business case is pretty easy. We're going to monetize that a thousand X better than existing hardware. So, then the question becomes, okay, great, that all makes sense, but can we actually do it? How do we build a better, more efficient computer? Well, biology (00:07:12) actually provides some proof for us here. So, the human brain, you may have heard this, runs on about 20 watts of energy. And what's even more remarkable to me is actually animal brains. So, that red number is how many neurons are in the brain. And if you kind of scale it linearly down to like a monkey's brain, it runs on one watt. To put that in perspective, the cell phone in your pocket runs on about one watt. And other animals like, you know, rats and bats and things like this, they run on milliwatts of energy. So, just something that's pretty relatable to everyone is a squirrel. You probably watched how accurate they can be. They jump between branches and they do it perfectly a thousand times out of a thousand. Their brain runs on eight milliwatts of energy. You could run over a hundred squirrel brains on your phone and it has very precise and accurate behavior. So, biology has created something quite (00:08:00) incredible. In fact, it's the right kind of physical substrate for intelligence. So, this is a quote I love. I don't feel like we truly understand something until we can create it. We've gotten a lot better creating intelligence systems. However, they do it in a kind of inefficient way. What kind of inefficiency is there? Well, as I kind of hinted at the beginning, most of the energy in a computing system goes into moving information around. Just to put some numbers on it, the human cortex, the squiggly part of your brain, the outside of it, only moves about 16 billion bits per second. That's actually kind of a small number if you think about it because there's, you know, some 13 or 14 billion neurons in that cortex. A GPU or, you know, a high-end computing system moves nearly 30 trillion bits in and out of memory (00:08:47) per second. That's outside the chip. Inside the chip, it's probably, you know, 10, 100x more than that. So, we're moving a lot more bits in these synthetic systems than the brain does. And that's actually what drives the energy demand. And, you know, how do we get here? You know, computers have been around for hundreds of years actually in some form. They were mechanical, they became analog around the turn of the century, and they became digital back in the 1930s, 1940s. So, the operation of that computer in 1940, 1945, is actually very similar to how they operate today. There's not a huge paradigm shift. They actually have this memory on the outside, you have some kind of computing, and you move bits back and forth. That operation creates a machine that just requires a lot of movement, but it's very fast. We built computers to be fast. They're always faster than the alternative. Incidentally, that computer in 1945 (00:09:38) that was built, called ENIAC, was built to do artillery trajectory calculation. And it was built to do it faster than the alternative. The alternative were humans who actually did the calculations. Now, the alternative typically is some other computer. This computer is twice the speed of that computer. That's how we sell computers. But it doesn't contemplate energy efficiency, and that's what we're changing. And, you know, these have been trends going on for a long time where the number of transistors kept going up. But we couldn't keep scaling the frequency. We couldn't keep scaling single-threaded performance. And now we're actually not scaling efficiency any longer. Moore's Law, if you may have heard of this, is like making transistors smaller, has largely ended. So, we're not seeing efficiency gains just from making transistors smaller. So, we need to rethink the problem a bit. So, how do we do it? Well, a good intuition is that we cut out the middleman. So, computers have been (00:10:29) built up with these abstractions. So, I mentioned digital. Digital means one and zero. That itself is an abstraction of the physical world. Like, we don't actually have systems that behave as one and zero. A transistor actually has states in the middle. But we engineer it to behave that way. And that's an abstraction. So, we kept building these abstractions up. And eventually, we started creating neural networks and learning machines on top of it. Each one of these abstractions actually is lossy. It means it's inefficient. It doesn't contemplate all the complexity underneath it. That's why it's an abstraction. So, what we're doing is kind of simplifying this in some sense. We find an abstraction of the physics of the semiconductor and connect that to the neural network. If you think about your brain for a moment, it has a bunch of neurons in it. But there's no linear algebra. There's (00:11:15) no floating-point math. It's actually the physics of the neurons give rise to intelligence. We want to kind of mimic some of that with the semiconductor. And this is also not a new concept. There's actually computation all throughout nature. Birds in a flock. You may have seen things like this where, you know, a bird does a simple behavior. It looks left, it looks right, and figures out where the next guy's going. And when they do that, they actually create these interesting flocking behaviors, this emergent behavior. And we see that with ant colonies. Ant colonies actually do intelligent things just by very simple rules. And this study is called dynamical systems theory. It's basically how I get these emergent properties from very simple behaviors of individual components. Our brain actually works this way as well. So we're taking (00:12:00) these ideas and actually starting to build circuits out of them. So let me give you an example of such a system. So everyone here probably knows what a metronome is. Just, you know, when you're learning to play the piano or something like that, it's just tick-tock, tick-tock, physical thing moving back and forth. So this is kind of cool. If you put multiple ones of them on a rigid plank, and that plank can just roll back and forth, you'll actually see them start to synchronize. And that's just due to the physics of the system. They each push against the plank just a little bit. And even if they're off by a little bit from each other, they're all synchronized to exactly the same phase. You can actually scale this up to hundreds of metronomes on a physical system, and they'll all synchronize. So this is actually a form of a dynamical system that goes through, you know, some starting point of all these different phases and always synchronizes. You can imagine a slightly more complicated version of this, (00:12:48) where maybe they don't all synchronize. Maybe half of them are synchronized with each other, another half are synchronized in an opposite pattern or something like this. But the idea is that this is a physical system that kind of behaves the way it does just by the inherent interconnection of the system itself. So we asked the question, can we actually use such a system like that metronome system to do computation? We want to connect that to generative AI. That's what we really care about. So we released a model we called UNO, which actually demonstrated this. It's an image generation model that's built on a set of oscillators like that. And we simulated it and made it open source so people can play with it. But this was the first demonstration that I can actually scale something up, train it, and actually get useful output like image generation. And you know, this is kind of some of the analysis that we (00:13:40) provided in that write-up. What you're seeing here is, we call it a state-space trajectory. It's basically how the system evolves in time. You can imagine if you characterize the state of the system as all the phases of those oscillators, and then look at how it evolves through time, and you basically condition that on the output. You say, I want to generate an airplane or a car or a bird. It'll actually go through different state-space trajectories. And so that's what we're seeing here is just an analysis of this. And these are actual images that were generated by it. Now, it turns out we actually started to build a lot of that fundamental science up over the last couple of months, and we found other things that enabled us to work even better. So this is a concept of what we call sparsity. Sparsity means that, you know, if I have, let's say I have a bunch of elements all connected to each other, like we have on the (00:14:28) left-hand side there. So, you know, if I have 10 elements and I want to connect them all to each other, I have 10 times 10 elements. So I have 100 connections. That's okay. But if I have 1,000, now I have 1,000 times 1,000, which becomes 1,000, so this doesn't scale very well. We call this n-squared scaling. So the more I add, it actually becomes way more hard to scale, right? So that's not great. So sparsity allows us to actually say, well, can I throw away some of those connections? If I throw them away, now can I actually rescue the behavior of the whole system? And it turns out you can actually not only throw away some of the connections, but you can actually get better behavior out of the whole system. It actually becomes more trainable. There's a lot of theoretical reasons for this, but we actually are able to do this in not only simulated systems, but actually real physical systems. So it's (00:15:15) one of these rare things where you get something that's more efficient, that's actually more scalable, and even gives you more performance. So this is kind of a holy grail. It's been a problem for a long time, but we had to frame the problem the right way to actually find this solution. And so this is actually the first time I'm talking about this publicly. I wanted to do it at this venue because I think it's a really big deal. This is actually the first physical dynamical computer ever built. We did this in five months. This company started in earnest in January. We didn't even have a team, but we said we're going to build this first physical prototype and do it this year. And actually we taped out the design, meaning we sent it to the fab on June 1st. The chip is back in our lab, (00:16:01) and we actually have results from it. So these are the first ever images generated from such a computer. Now, great, cool, but does it do anything useful beyond just images? You can actually do any kind of a task like sequence modeling or language models. But the interesting thing here is it's only 500 or so nanojoules per image. So to put that in perspective, a normal computer like a GPU is on the order of millijoules. So nanojoules is 10 to the minus ninth. It's really, really small. So it's many orders of magnitude more efficient than a standard computer. And it's because it just doesn't move information around. This is proof positive this works. So this is literally the first time we're talking about it publicly. So yeah, thank you. (00:16:50) So what's cool here is this is really the emergence of something new. So computers have gone from CPUs to GPUs going more and more parallel to compute and memory, which is even more parallel and fine-grained. But all of these are what we call von Neumann architecture. They have a memory and compute, and we move information back and forth. What we built is what's called a dynamical computer, which actually has compute and memory in one thing. We don't have a memory interface. Each individual computing element is a memory. There's a completely different way to look at the problem. And so we call this 4D computing, where we use the time dimension and the dynamics, and we actually use the physical three dimensions of die stacking, putting things vertically, as well as in a planar form. So we have three dimensions from the physical, and we have one dimension in time. So this is actually kind of a new way of thinking about a computer, and it really is proving to work (00:17:38) for efficiency's sake. So now, what are the implications if we build something that's a thousand times more power efficient? I think this is actually pretty cool. So intelligence per watt is what we care about. Can we optimize this and make it better over time? There is actually a thermodynamic limit, which you can never exceed. And the mammalian brains, so animal brains, are somewhere within one or two orders of magnitude of that. Today, we're on the far left of this graph, and we're about 10 billion times away. That's one with 10 zeros after it from that thermodynamic limit. We think in that three and a half years, we can hit the limits of 2D lithography. And the overarching goal of this company is to beat biology. We want to make something better and enable, you know, compute everywhere, including compute in new robotic forms and things like this in the next decade or so. (00:18:32) I think what will be interesting is that we'll see the shift going from like big, big data centers with gigawatts to many small data centers all over the place. I think this is a good thing. It actually makes things that are more environmentally friendly, more local, more adaptive. And as I said, I think enabling the ability to build billions of robots that kind of dynamically assemble to solve problems in our world is something that I think is actually really cool. This is something that will enable us to think about bigger problems and do even more. And, you know, I talked about AI being a trillion dollar market. Well, if we disrupt it by a thousand X, there's a concept called Jeevan's paradox where when you drop the underlying cost of an asset, you actually consume more than the drop of that asset. So if you make something half the price, (00:19:20) you'll consume more than 2X. If you make something one one thousandth the price, you'll consume more than one one thousandth of it. And I think this will create the largest market that humanity's ever seen. I mean, that was extremely unexpected. I got to say. Let me let me start with actually probably the thing that's on everybody's mind, which is to the extent that this works, I mean, you probably saw Jensen earlier. There just needs to be an entire ecosystem of people that are beside you and around you, whether it's the fabs, packagers, et cetera, et cetera. What does it take to get from this early version to something that sits in somebody's hand or that people use? And how do you see that path in terms of time and complexity? What does that look like? Yeah. Time-wise, we're within two years (00:20:08) of getting it to a full product. I mean, there's a lot of... And what is the product? Yeah, it's a VM that sits somewhere that you guys manage. Effectively. We're building a new data center product for us. So it's a whole rack. It's a system. Right. And the idea is that basically we'll run those models on it. And so tokens in, tokens out through a network cable, but the inner guts are completely different than an existing computer. And do you expect that you'll have to move to support the existing model families and existing architectures? And will this work in a world where, you know, we've spent all of this time like, okay, KVCache and let's all... Like this all just so mechanically reductive based on, as you said, these abstractions that we've lived on. Right. So how do you expect the rest of us to kind of move towards this? Because I mean, I think you see that efficiency curve we'd all want it. So how do we take advantage of it? Yeah. So I think there's a sliding scale (00:20:57) between, you know, how much better something is and how much pain you'll take to move to it. And, you know, I basically took the attack of like, let's make it really, really compelling to move. There is going to be some work to port things over. We actually don't port at the operations layer. You port the model layer. So yes, the existing models will work, but there's a fair bit of compute required to make that transition happen. And very basic elements like MatMul, does that exist in your... It doesn't exist. I mean, you can characterize it as MatMul, but it doesn't implement it as MatMul. Okay. It implements it as a sort of time varying behavior. But each one of those time steps you can analyze is basically a matrix of the current state times a transition matrix. And when you're building a team like this, like, who are these people? These are biologists plus physicists plus what are these people? Yes. Like, it's sort of like theorists that come up with (00:21:46) these, like, dynamical systems theory has been around for a hundred years. So we got people from that world. And then we got people who actually build chips and they don't talk to each other. They don't talk to each other. So we had to facilitate that. That's actually one of the most challenging things about this company is the span of talents that we have is so big that getting them to kind of all coordinate and build one thing is actually pretty hard. Well, and what is this like CUDA-like equivalent, if you will, just to use a bad analogy, that allows these people up here to talk to these people down there? Yeah. So we actually have built a set of libraries in Python. In Python. It's Python. It's not CUDA, but it's, you know, it's a language of sorts that allows you to kind of express time varying elements that have stochastic behavior. I mean, it's incredibly impressive. It's so ambitious. Thank you very much. It's great to see you. Great to see you.

本集资源与出处