WEBVTT - How to Build the Ultimate GPU Cloud to Power AI

0:00:10.160 --> 0:00:14.400
<v Speaker 1>Hello, and welcome to another episode of the Odd Lots Podcast.

0:00:14.480 --> 0:00:16.680
<v Speaker 2>I'm Joe Wisenthal and I'm Tracy Alloway.

0:00:16.800 --> 0:00:19.360
<v Speaker 1>Tracy, have you looked at in video stock chart lately?

0:00:19.440 --> 0:00:21.080
<v Speaker 1>And by lately, I don't mean like over the last

0:00:21.120 --> 0:00:22.680
<v Speaker 1>two years. I mean like just like over the last

0:00:22.720 --> 0:00:24.520
<v Speaker 1>like two weeks or two months.

0:00:24.560 --> 0:00:26.400
<v Speaker 2>I don't need to look at it because everyone keeps

0:00:26.440 --> 0:00:28.760
<v Speaker 2>talking about it. So I know, I know what's happening.

0:00:28.960 --> 0:00:30.880
<v Speaker 1>You know what, I'm pretty happy about. Could I just say,

0:00:31.160 --> 0:00:33.960
<v Speaker 1>you know, we did that episode like two months ago, yes,

0:00:34.200 --> 0:00:37.519
<v Speaker 1>with Stacy Raskin, and we were like, what's what's up

0:00:37.520 --> 0:00:39.239
<v Speaker 1>a good video, like well, you know, I know it's

0:00:39.240 --> 0:00:42.920
<v Speaker 1>at the center of the AI chips boom and whatever.

0:00:43.479 --> 0:00:45.199
<v Speaker 1>And then like we did that episode and it came

0:00:45.200 --> 0:00:46.680
<v Speaker 1>out and then a week later like they just like

0:00:46.800 --> 0:00:47.600
<v Speaker 1>knocked it out of the park.

0:00:48.479 --> 0:00:49.639
<v Speaker 3>Yeah, so you.

0:00:49.640 --> 0:00:51.000
<v Speaker 2>Know, we were early.

0:00:51.880 --> 0:00:53.640
<v Speaker 3>We were at least like, you know, a good like

0:00:53.680 --> 0:00:54.400
<v Speaker 3>two weeks earlier.

0:00:55.160 --> 0:00:56.840
<v Speaker 2>Hey, hey, two weeks I'll take it.

0:00:57.440 --> 0:00:58.360
<v Speaker 3>I'll take it.

0:00:58.440 --> 0:01:01.800
<v Speaker 1>So clearly something that you know, we and we talked

0:01:01.800 --> 0:01:03.760
<v Speaker 1>about this with Stacy, like you know, something that in

0:01:03.840 --> 0:01:06.840
<v Speaker 1>Nvidia has is like everyone's trying to buy it. Everyone's

0:01:06.840 --> 0:01:08.839
<v Speaker 1>trying to get it, But then it raises the next

0:01:08.880 --> 0:01:11.240
<v Speaker 1>question of like, okay, but what is that market? Like

0:01:11.520 --> 0:01:12.560
<v Speaker 1>how do you buy a chip?

0:01:13.000 --> 0:01:14.959
<v Speaker 2>Yeah? How do you buy a chip? And then I

0:01:14.959 --> 0:01:17.080
<v Speaker 2>guess what do you actually do with it once you

0:01:17.200 --> 0:01:19.280
<v Speaker 2>have it? Because my impression is that for a lot

0:01:19.319 --> 0:01:23.279
<v Speaker 2>of these AI applications, the way you use the chips,

0:01:23.319 --> 0:01:26.119
<v Speaker 2>the way you set up the data centers is very,

0:01:26.240 --> 0:01:29.399
<v Speaker 2>very different to what we've seen in the past. And

0:01:29.440 --> 0:01:32.280
<v Speaker 2>I think also what in Vidia is doing now is

0:01:32.360 --> 0:01:34.959
<v Speaker 2>kind of different. But maybe we can get into this

0:01:35.040 --> 0:01:36.920
<v Speaker 2>with our guests. My impression is they're trying to create

0:01:37.280 --> 0:01:40.960
<v Speaker 2>a sort of like holistic approach for customers where they

0:01:41.000 --> 0:01:44.840
<v Speaker 2>provide not just the hardware, but also some services to

0:01:44.880 --> 0:01:45.680
<v Speaker 2>go along with it.

0:01:46.000 --> 0:01:48.720
<v Speaker 1>Yes, right, and like all the software and Stacy talked

0:01:48.760 --> 0:01:50.880
<v Speaker 1>about that with the Kuda ecosystemica that.

0:01:50.840 --> 0:01:53.160
<v Speaker 3>Was it, how dominant that is? But right, like what

0:01:53.200 --> 0:01:55.360
<v Speaker 3>do you do with it? Like how do you get one? If?

0:01:55.400 --> 0:01:56.800
<v Speaker 3>Like what you know, what would we do.

0:01:56.760 --> 0:02:00.760
<v Speaker 1>Tracy if a big palette of in Vidia chips wound

0:02:00.840 --> 0:02:01.840
<v Speaker 1>up here?

0:02:01.480 --> 0:02:03.920
<v Speaker 2>Do you want to know a secret? Yeah, my basement

0:02:03.960 --> 0:02:06.600
<v Speaker 2>is filled with h one hundred chips. Just got a

0:02:06.640 --> 0:02:08.080
<v Speaker 2>pile of them. It came with the house.

0:02:08.440 --> 0:02:10.880
<v Speaker 1>It was on that ship that was stuck off the Chesapeake,

0:02:10.960 --> 0:02:12.960
<v Speaker 1>and instead of getting your cowards, you got it.

0:02:13.080 --> 0:02:15.720
<v Speaker 2>I just caught a palette of age four hundreds.

0:02:15.440 --> 0:02:19.680
<v Speaker 1>That that well, we're manifesting that into reality. So anyway,

0:02:19.760 --> 0:02:22.600
<v Speaker 1>I like how this world works so essentially, like the

0:02:22.800 --> 0:02:27.160
<v Speaker 1>trading and dealing of these, like the hottest commodity in

0:02:27.200 --> 0:02:30.920
<v Speaker 1>the world right which is these these advanced chips from AI,

0:02:31.000 --> 0:02:32.920
<v Speaker 1>and how that works and who can get one? I

0:02:32.960 --> 0:02:35.520
<v Speaker 1>still think is like a sort of mystery that we

0:02:35.639 --> 0:02:38.160
<v Speaker 1>need to delve further into this question.

0:02:38.400 --> 0:02:40.359
<v Speaker 2>I agree, And there is also there's a lot of

0:02:40.440 --> 0:02:43.600
<v Speaker 2>excitement around it right now for the obvious reasons of

0:02:43.680 --> 0:02:48.239
<v Speaker 2>everyone's really into generative AI and in video stock is exploding,

0:02:48.240 --> 0:02:50.640
<v Speaker 2>as we already talked about, but we're also seeing a

0:02:50.680 --> 0:02:55.560
<v Speaker 2>lot of previous I guess consumers of chips, like the

0:02:55.600 --> 0:02:59.079
<v Speaker 2>crypto miners start to pivot into the space, and I'd

0:02:59.080 --> 0:03:01.720
<v Speaker 2>be curious to see what they're doing in it as well,

0:03:01.800 --> 0:03:04.960
<v Speaker 2>and how much of that is just you know, desperation

0:03:05.520 --> 0:03:08.959
<v Speaker 2>versus versus a real business opportunity.

0:03:08.440 --> 0:03:09.440
<v Speaker 3>In the video game market.

0:03:09.520 --> 0:03:11.079
<v Speaker 2>Yeah, oh totally, I forgot about.

0:03:11.160 --> 0:03:13.320
<v Speaker 1>Which was like the other thing. It's like, for years

0:03:13.360 --> 0:03:15.519
<v Speaker 1>I thought of Nvidia is the video game company. Yeah,

0:03:15.560 --> 0:03:17.639
<v Speaker 1>because they had their logo on xboxes.

0:03:17.720 --> 0:03:21.680
<v Speaker 2>And how realistic is that pivot? What proportion of those

0:03:21.720 --> 0:03:23.840
<v Speaker 2>types of chips can be used for AI?

0:03:24.000 --> 0:03:27.080
<v Speaker 1>Now, well, I'm very excited. We do have I believe

0:03:27.240 --> 0:03:29.400
<v Speaker 1>the perfect guest. We are going to be speaking with

0:03:29.440 --> 0:03:32.919
<v Speaker 1>Brandon McBee. He is the chief strategy officer and co

0:03:33.000 --> 0:03:36.720
<v Speaker 1>founder of core Weave, which is a specialized cloud services

0:03:36.800 --> 0:03:40.680
<v Speaker 1>provider that's basically providing this sort of like high volume

0:03:40.800 --> 0:03:45.160
<v Speaker 1>compute to AI type companies. They recently raised over four

0:03:45.240 --> 0:03:47.560
<v Speaker 1>hundred million dollars. Have been in this space for a

0:03:47.600 --> 0:03:50.280
<v Speaker 1>little while. So Brandon, thank you so much for coming

0:03:50.320 --> 0:03:51.160
<v Speaker 1>on odd lots.

0:03:51.520 --> 0:03:53.640
<v Speaker 4>Thanks for the opportunity. Guys, really excited to chat with

0:03:53.640 --> 0:03:54.160
<v Speaker 4>you all today.

0:03:54.720 --> 0:03:57.240
<v Speaker 1>So let's just let me sorry if Tracy and I, like,

0:03:57.360 --> 0:03:58.880
<v Speaker 1>I don't know why they would do this, but if

0:03:58.920 --> 0:04:00.880
<v Speaker 1>like some VC was like, you know, we want you

0:04:00.960 --> 0:04:03.680
<v Speaker 1>to do on launch GPT. We want you to like

0:04:03.800 --> 0:04:07.880
<v Speaker 1>do a pore base large language model off of all

0:04:07.920 --> 0:04:09.640
<v Speaker 1>the work you've done. We want you to compete with

0:04:09.720 --> 0:04:12.240
<v Speaker 1>open AI. And they gave us like I don't know

0:04:12.440 --> 0:04:15.400
<v Speaker 1>some like, you know, one hundred million dollar rays, they said,

0:04:15.440 --> 0:04:18.640
<v Speaker 1>go start, do your startup? Could I call in video

0:04:19.320 --> 0:04:21.560
<v Speaker 1>and buy chips? Would I be able to get in

0:04:21.600 --> 0:04:22.120
<v Speaker 1>the door there?

0:04:22.600 --> 0:04:25.440
<v Speaker 4>Gosh? I mean you're I think you and everyone else

0:04:25.800 --> 0:04:27.960
<v Speaker 4>is asking that question, and you're going to have a

0:04:28.240 --> 0:04:31.039
<v Speaker 4>huge problem doing that. Right now, it's mostly just around

0:04:31.720 --> 0:04:35.520
<v Speaker 4>how much in demand this infrastructure became, right I mean,

0:04:35.600 --> 0:04:38.599
<v Speaker 4>you could argue it's one of the most critical pieces

0:04:38.600 --> 0:04:41.840
<v Speaker 4>of information technology resources on the planet right now and

0:04:42.400 --> 0:04:45.279
<v Speaker 4>suddenly everyone needs it, and you know, I like to

0:04:45.279 --> 0:04:49.800
<v Speaker 4>contextualize it in that, you know, the piece of software

0:04:49.800 --> 0:04:53.080
<v Speaker 4>adoption for AIS like one of the fastest adoption curves

0:04:53.080 --> 0:04:57.440
<v Speaker 4>we've ever seen, right Like, you're you're hitting these milestones

0:04:57.480 --> 0:05:01.280
<v Speaker 4>faster than any other software platform previously, and now all

0:05:01.320 --> 0:05:04.560
<v Speaker 4>of a sudden, you're asking infrastructure build to keep up

0:05:04.600 --> 0:05:07.360
<v Speaker 4>with that, right a space that traditionally takes more time,

0:05:07.480 --> 0:05:12.120
<v Speaker 4>and it's created this massive supply demand and balance just

0:05:12.200 --> 0:05:16.280
<v Speaker 4>on in place infrastructure today and not only infratructure is

0:05:16.279 --> 0:05:20.560
<v Speaker 4>available to purchase, and it's an issue that is going

0:05:20.600 --> 0:05:22.480
<v Speaker 4>to be ongoing for a bit as well, we think.

0:05:23.360 --> 0:05:26.479
<v Speaker 2>So can I ask the basic question, which is core weave.

0:05:27.400 --> 0:05:30.880
<v Speaker 2>What do you do exactly? Joe mentioned the capital raise,

0:05:30.920 --> 0:05:33.320
<v Speaker 2>which I think has you valued at something like two

0:05:33.320 --> 0:05:37.719
<v Speaker 2>billion dollars, So congrats, but what exactly are you doing here?

0:05:38.160 --> 0:05:41.400
<v Speaker 4>Yeah? Thank you. So Corey is a specialized cloud service

0:05:41.400 --> 0:05:45.920
<v Speaker 4>provider that is focused on highly parallelizable workloads. So we

0:05:46.320 --> 0:05:50.440
<v Speaker 4>build and operate the world's most performant GPU infrastructure at

0:05:50.480 --> 0:05:54.760
<v Speaker 4>scale and predominantly serve three sectors. That's the artificial intelligence sector,

0:05:54.920 --> 0:05:58.520
<v Speaker 4>the media and entertainment sector, and the computational chemistry sector.

0:05:58.640 --> 0:06:04.320
<v Speaker 4>So we build specialize in building this infrastructure at supercompute scale.

0:06:04.480 --> 0:06:07.560
<v Speaker 4>It's like quite literally, you know, it's sixteen thousand GPU

0:06:07.760 --> 0:06:09.640
<v Speaker 4>fabric and we can get into all the details and

0:06:09.680 --> 0:06:12.200
<v Speaker 4>how complex that is. But we build that so that

0:06:12.320 --> 0:06:16.280
<v Speaker 4>entities can come in and train these next generation foundation

0:06:16.440 --> 0:06:19.040
<v Speaker 4>machine learning models on. And you know, we found ourselves

0:06:19.080 --> 0:06:20.760
<v Speaker 4>in a spot where we can do that better than

0:06:20.880 --> 0:06:23.279
<v Speaker 4>literally anyone else in the market and do it on

0:06:23.320 --> 0:06:27.159
<v Speaker 4>a timeline that's faster or I think the only entity

0:06:27.200 --> 0:06:32.080
<v Speaker 4>with H one hundred available to clients at scale globally today.

0:06:32.800 --> 0:06:35.120
<v Speaker 2>So you have an actual basement full of H one

0:06:35.200 --> 0:06:38.960
<v Speaker 2>hundred chips. Well, can you talk to us. You know,

0:06:39.040 --> 0:06:42.560
<v Speaker 2>when you say infrastructure, we help clients build out the infrastructure,

0:06:42.640 --> 0:06:47.599
<v Speaker 2>help us conceptualize this. What does what does the infrastructure

0:06:48.080 --> 0:06:51.880
<v Speaker 2>for this type of AI actually look like? And how

0:06:51.880 --> 0:06:55.720
<v Speaker 2>does it differ to infrastructure for other types of large

0:06:55.720 --> 0:06:57.440
<v Speaker 2>scale technology projects.

0:06:57.920 --> 0:07:01.000
<v Speaker 4>Yeah, totally, so, you know, I I think during the

0:07:01.080 --> 0:07:04.200
<v Speaker 4>last in video quarterly earnings called Jensen put this a

0:07:04.200 --> 0:07:06.839
<v Speaker 4>really great way in the Q and A section, he

0:07:06.960 --> 0:07:10.000
<v Speaker 4>said that we are at the first year of a

0:07:10.120 --> 0:07:13.760
<v Speaker 4>decade long modernization of the data center, or like making

0:07:13.760 --> 0:07:16.640
<v Speaker 4>the data center intelligent. Right, you can kind of you

0:07:16.640 --> 0:07:19.840
<v Speaker 4>could suggest that the last generation or the twenty tens

0:07:20.040 --> 0:07:23.280
<v Speaker 4>data center was comprised of CPU, compute, storage and these

0:07:23.320 --> 0:07:26.840
<v Speaker 4>things that didn't really work together that intelligently. And the

0:07:26.880 --> 0:07:29.880
<v Speaker 4>way that in Nvidia has positioned itself is to make

0:07:29.880 --> 0:07:32.320
<v Speaker 4>it a smart data center that's like smart routing of

0:07:32.480 --> 0:07:36.160
<v Speaker 4>data packets of different pieces of infrastructure in there. That's

0:07:36.200 --> 0:07:39.680
<v Speaker 4>all focused on how do you expand the throughput in

0:07:39.720 --> 0:07:46.440
<v Speaker 4>communicability of and between pieces of infrastructure. Right, It's just

0:07:46.840 --> 0:07:50.840
<v Speaker 4>an amazingly different approach to data center deployments. And so

0:07:51.680 --> 0:07:54.160
<v Speaker 4>the way that we're building it and we're working with

0:07:54.480 --> 0:07:58.360
<v Speaker 4>Nvidia infrastructure. We design everything to a DGX reference back

0:07:58.400 --> 0:08:01.160
<v Speaker 4>in dgx's in videos like how do you draw the

0:08:01.200 --> 0:08:04.720
<v Speaker 4>most performance out of Nvidia infrastructure is possible with all

0:08:04.720 --> 0:08:08.000
<v Speaker 4>the anciliary components associated with it. So all this stuff

0:08:08.040 --> 0:08:10.960
<v Speaker 4>is going into what's qualified as a Tier three or

0:08:11.000 --> 0:08:14.440
<v Speaker 4>a Tier four data center. We collocate with within these things,

0:08:14.440 --> 0:08:17.520
<v Speaker 4>so we're not quite building in a basement, even though

0:08:17.800 --> 0:08:21.400
<v Speaker 4>like in our past history we certainly you know, had

0:08:21.840 --> 0:08:24.640
<v Speaker 4>time doing that, but this is within you know, just

0:08:25.120 --> 0:08:28.640
<v Speaker 4>amazing collocation sites that are operated by our partners such

0:08:28.640 --> 0:08:30.800
<v Speaker 4>as switch right. So a Tier three a Tier four

0:08:30.920 --> 0:08:35.680
<v Speaker 4>site is something that's qualified based on its ability to

0:08:35.720 --> 0:08:39.480
<v Speaker 4>serve workloads with an extremely high uptime. So we're talking

0:08:39.520 --> 0:08:43.840
<v Speaker 4>like ninety nine point nine nine percent uptime rate, and

0:08:43.880 --> 0:08:49.760
<v Speaker 4>that's guaranteed by its power redundancy, it's Internet redundancy, and

0:08:49.800 --> 0:08:53.480
<v Speaker 4>its security and then ultimately like it's connectivity to the

0:08:53.559 --> 0:08:56.959
<v Speaker 4>Internet backbone. Right, So as it's like, as a first step,

0:08:57.360 --> 0:09:02.520
<v Speaker 4>you're housed within these data centers that are just critical

0:09:02.600 --> 0:09:06.880
<v Speaker 4>parts of the Internet infrastructure, and then from there you

0:09:06.920 --> 0:09:09.079
<v Speaker 4>start building out the servers within there. And I can

0:09:09.240 --> 0:09:10.160
<v Speaker 4>go into that detail.

0:09:10.600 --> 0:09:13.320
<v Speaker 1>So you mentioned actually I want to just get sort

0:09:13.320 --> 0:09:15.480
<v Speaker 1>of defined some terms. Can you just real quickly before

0:09:15.520 --> 0:09:17.240
<v Speaker 1>we move on Tier three tier four?

0:09:17.240 --> 0:09:18.080
<v Speaker 3>What do you mean by this?

0:09:18.880 --> 0:09:21.880
<v Speaker 4>Yeah? So tier three, tier four. This all goes back

0:09:21.920 --> 0:09:24.360
<v Speaker 4>to like the quality of the data center that you're

0:09:24.360 --> 0:09:26.760
<v Speaker 4>in it. It's all about the reliability and up time

0:09:26.880 --> 0:09:28.640
<v Speaker 4>that you should be able to achieve out of that

0:09:28.760 --> 0:09:32.600
<v Speaker 4>data center. It's another way to qualify the services around it.

0:09:32.600 --> 0:09:35.960
<v Speaker 4>It's like power. You get redundant power, right like multiple

0:09:35.960 --> 0:09:39.880
<v Speaker 4>power services in case one goes offline, there's another one

0:09:40.080 --> 0:09:44.320
<v Speaker 4>you get, you know, redundant cooling, you get redundant Internet connectivity.

0:09:44.360 --> 0:09:47.480
<v Speaker 4>It's all these services that like have extra fiil safs

0:09:47.840 --> 0:09:50.760
<v Speaker 4>that allow for you to operate at the highest up

0:09:50.800 --> 0:09:52.400
<v Speaker 4>time and security level possible.

0:09:52.640 --> 0:09:54.760
<v Speaker 1>Is higher tier better? Like tier three four? Is that

0:09:54.800 --> 0:09:56.120
<v Speaker 1>better than Tier one and tier two?

0:09:57.040 --> 0:09:57.760
<v Speaker 4>That's correct?

0:09:57.960 --> 0:10:01.400
<v Speaker 1>Okay, so quick follow up question. Then you know we're

0:10:01.400 --> 0:10:03.280
<v Speaker 1>interested in, like, okay, where the rubber hits the road.

0:10:03.280 --> 0:10:08.040
<v Speaker 1>The scarcity is here. Let's say Tracy miraculously opens her

0:10:08.120 --> 0:10:10.400
<v Speaker 1>basement and there really is like you know, all these

0:10:10.440 --> 0:10:14.480
<v Speaker 1>palettes of these video chips, there is there capacity at

0:10:14.520 --> 0:10:16.440
<v Speaker 1>the data centers right now, She's like, you know, what

0:10:16.440 --> 0:10:19.120
<v Speaker 1>we want to co locate with you. You guys have great power,

0:10:19.679 --> 0:10:22.080
<v Speaker 1>pretty well connected to the internet. You have like good

0:10:22.120 --> 0:10:24.920
<v Speaker 1>security guards. So there's operated twenty four to seven. We

0:10:24.920 --> 0:10:27.000
<v Speaker 1>want to set something up, like is there space there?

0:10:28.240 --> 0:10:30.839
<v Speaker 4>Yeah, it's a fantastic question. It's a it's an issue

0:10:30.840 --> 0:10:33.480
<v Speaker 4>that didn't really pop up until really in the last

0:10:33.559 --> 0:10:34.560
<v Speaker 4>eight weeks or so.

0:10:34.800 --> 0:10:37.760
<v Speaker 3>Oh, it's really happening that fast.

0:10:38.400 --> 0:10:39.760
<v Speaker 4>It's happening that fast, Joe.

0:10:39.880 --> 0:10:40.880
<v Speaker 3>And it's okay, So.

0:10:40.960 --> 0:10:43.440
<v Speaker 2>That we said the two week lead time on in

0:10:43.520 --> 0:10:45.080
<v Speaker 2>video was very important, Joe.

0:10:45.360 --> 0:10:48.400
<v Speaker 3>Yeah, you're right, you're right. Is wow? Wait what happened?

0:10:48.600 --> 0:10:48.800
<v Speaker 4>Wait?

0:10:49.240 --> 0:10:52.600
<v Speaker 1>What happened sixteen described? Sixteen weeks ago?

0:10:52.720 --> 0:10:53.760
<v Speaker 3>Verus eight weeks ago?

0:10:54.520 --> 0:10:57.720
<v Speaker 4>Sure, it even last year? Right, So this is a space,

0:10:57.760 --> 0:11:02.240
<v Speaker 4>the data centers space, collocation space that's been fairly chronically

0:11:02.360 --> 0:11:05.440
<v Speaker 4>underinvested in because the Hyperscale has just built out their

0:11:05.480 --> 0:11:09.680
<v Speaker 4>own data centers, right instead. But what's happened is the

0:11:09.760 --> 0:11:13.600
<v Speaker 4>infrastructure changed. The type of compute that we're putting in

0:11:13.640 --> 0:11:17.240
<v Speaker 4>these data centers, it's different than the last generation, right,

0:11:17.280 --> 0:11:20.800
<v Speaker 4>so we're predominantly focused on GPU compute instead of CPU

0:11:20.840 --> 0:11:25.439
<v Speaker 4>compute and GPU compute. It's about four times more power

0:11:25.559 --> 0:11:29.839
<v Speaker 4>dance than CPU compute, and that throws the data center

0:11:29.960 --> 0:11:33.440
<v Speaker 4>planning into chaos, right because ultimately, let's say you have

0:11:33.480 --> 0:11:36.319
<v Speaker 4>a ten thousand square foot room in the data center, right,

0:11:36.360 --> 0:11:38.160
<v Speaker 4>and you have a certain amount of power it's called

0:11:38.160 --> 0:11:39.960
<v Speaker 4>one hundred units of power that go into that ten

0:11:40.000 --> 0:11:44.079
<v Speaker 4>thousand square feet. Well, because I'm four times more power DNS,

0:11:44.760 --> 0:11:47.320
<v Speaker 4>it means that now I take those hundred units of power,

0:11:47.400 --> 0:11:50.560
<v Speaker 4>but I only require about twenty five percent of that

0:11:50.640 --> 0:11:53.439
<v Speaker 4>data center footprint or in other words, twenty five hundred

0:11:53.440 --> 0:11:56.400
<v Speaker 4>square feet within that ten thousand square foot footprint. So

0:11:56.800 --> 0:12:00.480
<v Speaker 4>that then leads to like, not only is the space

0:12:00.760 --> 0:12:03.960
<v Speaker 4>in the data center being used inefficiently now because you

0:12:04.240 --> 0:12:06.720
<v Speaker 4>theoretically have to run more power into the data center

0:12:06.800 --> 0:12:08.800
<v Speaker 4>to use that full ten thousand square feet due to

0:12:08.800 --> 0:12:12.360
<v Speaker 4>the Poara density delta, but now you have cooling issues,

0:12:12.960 --> 0:12:15.720
<v Speaker 4>right because you designed that footprint to be able to

0:12:15.720 --> 0:12:19.920
<v Speaker 4>cool ten thousand square feet spread out across that entire area.

0:12:20.000 --> 0:12:21.040
<v Speaker 4>But now you're dropping storry.

0:12:21.559 --> 0:12:23.640
<v Speaker 1>Sorry, I just want to back up because this is

0:12:23.880 --> 0:12:26.040
<v Speaker 1>extremely interesting, so I don't want to I just want

0:12:26.080 --> 0:12:27.079
<v Speaker 1>to get this detail right.

0:12:27.640 --> 0:12:30.840
<v Speaker 3>Just sorry, just to and then move on.

0:12:30.920 --> 0:12:34.439
<v Speaker 1>But the let's given an x amount of power at

0:12:34.480 --> 0:12:37.720
<v Speaker 1>one hundred units of power. What you're saying is that

0:12:37.800 --> 0:12:41.880
<v Speaker 1>with this next generation of compute, it now only gets

0:12:42.120 --> 0:12:42.720
<v Speaker 1>that's now.

0:12:42.600 --> 0:12:44.720
<v Speaker 3>Only sufficient for a quarter of the data center.

0:12:44.760 --> 0:12:48.040
<v Speaker 1>In other words, that to power that whole that space,

0:12:48.520 --> 0:12:50.800
<v Speaker 1>and that to then power the whole space, you really

0:12:50.840 --> 0:12:52.360
<v Speaker 1>would need like four x the power.

0:12:53.320 --> 0:12:57.160
<v Speaker 4>That's accurate. Okay. The complication really arises out of the

0:12:57.160 --> 0:13:00.400
<v Speaker 4>cooling that that's required from that, right, So if you

0:13:00.400 --> 0:13:03.160
<v Speaker 4>imagine you can cool a ten thousand square foot space

0:13:03.160 --> 0:13:05.400
<v Speaker 4>and you designed for that, that's one thing. But now

0:13:05.440 --> 0:13:08.080
<v Speaker 4>if you have to cool in a much more dense area,

0:13:08.559 --> 0:13:12.400
<v Speaker 4>that's a different type of cooling requirement. And so that's

0:13:12.480 --> 0:13:15.719
<v Speaker 4>led to this issue where there's only a certain subset

0:13:15.960 --> 0:13:18.640
<v Speaker 4>of Tier three and four data centers across the US

0:13:19.120 --> 0:13:23.440
<v Speaker 4>that can are currently designed for or can quickly be

0:13:23.559 --> 0:13:27.880
<v Speaker 4>designed and changed to be able to accommodate this new

0:13:27.960 --> 0:13:31.760
<v Speaker 4>power density issue. So now not only like if you

0:13:31.840 --> 0:13:34.440
<v Speaker 4>had all those eighth one hundreds in your basement, you

0:13:34.520 --> 0:13:36.480
<v Speaker 4>might not have a place to plug them into. And

0:13:37.320 --> 0:13:40.160
<v Speaker 4>that's become a pretty big problem for the industry very quickly,

0:13:40.160 --> 0:13:42.520
<v Speaker 4>and truly has only arisen in the last eight weeks

0:13:42.640 --> 0:13:45.120
<v Speaker 4>or so, and it's going to persist for a few quarters.

0:13:46.040 --> 0:13:50.040
<v Speaker 2>So you were describing the difference between CPU and GPU.

0:13:50.600 --> 0:13:54.600
<v Speaker 2>How do you actually connect these newer types or these

0:13:54.640 --> 0:13:58.600
<v Speaker 2>different types of chips together, because I imagine, you know,

0:13:58.760 --> 0:14:01.160
<v Speaker 2>old data centers you just have a bunch of like

0:14:01.240 --> 0:14:04.520
<v Speaker 2>Ethernet cables or something like that. But for this type

0:14:04.559 --> 0:14:06.640
<v Speaker 2>of processing power, do you need something different?

0:14:08.000 --> 0:14:12.160
<v Speaker 4>That's exactly correct, Chracy. So what we so the legacy

0:14:12.280 --> 0:14:15.240
<v Speaker 4>the generalized compute data centers are really what the hyperscalers

0:14:15.280 --> 0:14:19.560
<v Speaker 4>look like. You know, Amazon, Google, Microsoft, Oracle. They predominantly

0:14:19.640 --> 0:14:23.240
<v Speaker 4>use something that's called Ethernet to connect all the service together.

0:14:23.280 --> 0:14:25.600
<v Speaker 4>And the reason you use that was, you know, you

0:14:25.600 --> 0:14:29.120
<v Speaker 4>don't really need to have high data throughput to connect

0:14:29.240 --> 0:14:31.040
<v Speaker 4>all these servers together, right, They just need to be

0:14:31.080 --> 0:14:33.040
<v Speaker 4>able to send some messages back and forth. They talk

0:14:33.080 --> 0:14:35.960
<v Speaker 4>to each other about what they're working on, but they're not,

0:14:36.480 --> 0:14:41.000
<v Speaker 4>you know, necessarily doing highly collaborative tasks that require moving

0:14:41.080 --> 0:14:44.720
<v Speaker 4>lots of data in between each other. That's changed. So

0:14:45.080 --> 0:14:48.160
<v Speaker 4>so today what people are focused on and need to

0:14:48.200 --> 0:14:52.400
<v Speaker 4>build are these effectively supercomputers. Right, and so we refer

0:14:52.520 --> 0:14:56.000
<v Speaker 4>to the connectivity between them, the network between them as

0:14:56.120 --> 0:14:59.560
<v Speaker 4>a fabric, right, it's called a network fabric. So if

0:14:59.600 --> 0:15:02.480
<v Speaker 4>we're build holding something to help train like the next

0:15:02.520 --> 0:15:07.600
<v Speaker 4>generation GPT model, typically clients are coming to us saying, hey,

0:15:07.640 --> 0:15:11.400
<v Speaker 4>I need a sixteen thousand GPU fabric of H one hundred.

0:15:11.960 --> 0:15:15.800
<v Speaker 4>So that's there's about eight GPUs that go into each server,

0:15:16.120 --> 0:15:18.960
<v Speaker 4>and then you have to run this connectivity between each

0:15:19.080 --> 0:15:21.240
<v Speaker 4>one of those servers. But it's now done in a

0:15:21.280 --> 0:15:25.480
<v Speaker 4>different way to your point, So we're using a in

0:15:25.520 --> 0:15:30.560
<v Speaker 4>Nvidio technology called InfiniBand which has the highest data throughput

0:15:30.680 --> 0:15:34.000
<v Speaker 4>to connect each of these devices together. And you know,

0:15:34.080 --> 0:15:38.560
<v Speaker 4>taking this sixteen thousand GPU cluster as an example, there's

0:15:38.600 --> 0:15:41.680
<v Speaker 4>two crazy numbers in here. One is that there are

0:15:41.960 --> 0:15:47.200
<v Speaker 4>forty eight thousand discrete connections that need to be made,

0:15:47.400 --> 0:15:50.280
<v Speaker 4>right like plugging one thing in from one computer to

0:15:50.320 --> 0:15:54.680
<v Speaker 4>another computer. But there's lots of switches and routers that

0:15:54.720 --> 0:15:57.200
<v Speaker 4>are between there. But you need to that forty eight

0:15:57.240 --> 0:16:03.120
<v Speaker 4>thousand times, and it takes over five hundred miles of

0:16:03.200 --> 0:16:07.200
<v Speaker 4>fiber optic cabling to do that successfully across the sixteen

0:16:07.240 --> 0:16:09.840
<v Speaker 4>thousand GPU cluster. And now again you're doing that within

0:16:09.880 --> 0:16:11.800
<v Speaker 4>a small space with a ton of power density, with

0:16:11.840 --> 0:16:14.720
<v Speaker 4>a ton of cooling, and it's just a completely different

0:16:14.760 --> 0:16:17.960
<v Speaker 4>way to build this infrastructure. It's just because the requirements

0:16:17.960 --> 0:16:20.560
<v Speaker 4>have changed, right, Like we've moved into this, like this

0:16:20.720 --> 0:16:25.040
<v Speaker 4>area where we are designing next generation AI models and

0:16:25.120 --> 0:16:27.840
<v Speaker 4>it requires a completely different type of compute, and it's

0:16:27.920 --> 0:16:31.320
<v Speaker 4>just it's caught the whole sector by surprise so much

0:16:31.360 --> 0:16:34.880
<v Speaker 4>so that you know, it's really challenging to go procure

0:16:34.880 --> 0:16:38.240
<v Speaker 4>it at the hyperscalers today because they didn't specialize in

0:16:38.280 --> 0:16:40.560
<v Speaker 4>building it. And that's you know where where core we've

0:16:40.560 --> 0:16:43.440
<v Speaker 4>comes in is we only focus on building this type

0:16:43.480 --> 0:16:46.240
<v Speaker 4>of compute for clients. It's our specialty. We hire all

0:16:46.240 --> 0:16:48.400
<v Speaker 4>of our engineering around it, all of our research goes

0:16:48.440 --> 0:16:51.040
<v Speaker 4>into it, and it's you know, it's been a fantastic

0:16:51.040 --> 0:16:53.640
<v Speaker 4>spot to be but our goal at the end of

0:16:53.640 --> 0:16:54.760
<v Speaker 4>the day is just to be able to get this

0:16:54.840 --> 0:16:57.480
<v Speaker 4>infrastructure into the hands of end consumers so that they

0:16:57.480 --> 0:17:00.640
<v Speaker 4>can build the amazing AI companies that have ones looking

0:17:00.680 --> 0:17:16.439
<v Speaker 4>forward to using and incorporating to enterprises and software companies.

0:17:21.520 --> 0:17:25.560
<v Speaker 2>You know, you mentioned these special or purpose built connections

0:17:25.680 --> 0:17:28.480
<v Speaker 2>that Nvidia is making, and this kind of leads nicely

0:17:28.640 --> 0:17:31.760
<v Speaker 2>into my next question, which is what exactly is your

0:17:31.880 --> 0:17:37.879
<v Speaker 2>relationship with Nvidia and in order to provide this type

0:17:37.960 --> 0:17:42.280
<v Speaker 2>of service, you know, vast amounts of processing power that

0:17:42.440 --> 0:17:46.080
<v Speaker 2>is well suited to a particular type of technology in

0:17:46.119 --> 0:17:49.160
<v Speaker 2>this case AI, do you have to have a really

0:17:49.200 --> 0:17:51.919
<v Speaker 2>good relationship with Nvidia to make that work? Like do

0:17:52.000 --> 0:17:55.120
<v Speaker 2>you have to have special access to H one, hundreds

0:17:55.160 --> 0:17:56.840
<v Speaker 2>and other chips.

0:17:57.840 --> 0:18:00.119
<v Speaker 4>It's a great question, and I'll try to offer or

0:18:00.680 --> 0:18:03.159
<v Speaker 4>from Nvidia's perspective, and it goes a little bit back

0:18:03.200 --> 0:18:05.160
<v Speaker 4>to the answer I just provided as well in that

0:18:06.200 --> 0:18:09.560
<v Speaker 4>I would think from in Nvidia's seat, what's most important

0:18:09.720 --> 0:18:13.640
<v Speaker 4>is empowering end users of their compute to be able

0:18:13.640 --> 0:18:18.200
<v Speaker 4>to access their compute and the most performant variant possible

0:18:19.160 --> 0:18:21.440
<v Speaker 4>at scale, and to be able to access it quickly, right,

0:18:21.480 --> 0:18:23.000
<v Speaker 4>Like a new generation comes out, they want to be

0:18:23.000 --> 0:18:25.240
<v Speaker 4>able to get their hands on it, right. And we've

0:18:25.320 --> 0:18:29.200
<v Speaker 4>built Core. We've around hitting every single one of those checkboxes. Right.

0:18:29.200 --> 0:18:31.440
<v Speaker 4>We build it at DGX reference back, we build it

0:18:31.560 --> 0:18:34.160
<v Speaker 4>at scale, and we bring it online on a timeline

0:18:34.200 --> 0:18:37.720
<v Speaker 4>that's you know, within months of a next generation chipset launch,

0:18:37.840 --> 0:18:41.680
<v Speaker 4>as opposed to you know, the more traditional legacy hyperscalers

0:18:41.680 --> 0:18:45.679
<v Speaker 4>that take quarters at a times, so US being in

0:18:45.720 --> 0:18:49.399
<v Speaker 4>a position to do that has has enabled us fantastic

0:18:49.640 --> 0:18:53.600
<v Speaker 4>access within Nvidia, and we have a history of consistently

0:18:53.640 --> 0:18:56.960
<v Speaker 4>executing on exactly what we've what we say we'll do right,

0:18:57.000 --> 0:19:02.120
<v Speaker 4>we under promise and over deliver as a business, and

0:19:02.520 --> 0:19:04.480
<v Speaker 4>I think that's just put us in this place where

0:19:04.800 --> 0:19:08.720
<v Speaker 4>Nvidia has the confidence in allocating infrastructure to us because

0:19:08.760 --> 0:19:10.680
<v Speaker 4>they know it's going to come online, they know it's

0:19:10.680 --> 0:19:14.240
<v Speaker 4>going to get to consumers faster than anyone else in

0:19:14.280 --> 0:19:15.760
<v Speaker 4>the market, and they know it's going to be delivered

0:19:15.760 --> 0:19:18.520
<v Speaker 4>in its most performance configuration that exists.

0:19:19.760 --> 0:19:22.359
<v Speaker 1>You know, I was thinking as I listened to some

0:19:22.400 --> 0:19:25.240
<v Speaker 1>of these answers, I keep having like these like imagines,

0:19:25.280 --> 0:19:29.520
<v Speaker 1>like you know, there's probably like some random industrial company

0:19:29.600 --> 0:19:32.159
<v Speaker 1>that's like traded like you know on the like S

0:19:32.200 --> 0:19:36.320
<v Speaker 1>and P four hundred that makes some cooling fluid whose

0:19:36.359 --> 0:19:38.080
<v Speaker 1>like sales are going to be up ten x. So

0:19:38.119 --> 0:19:40.040
<v Speaker 1>I'm like googling while we're talking, like what is a

0:19:40.040 --> 0:19:42.000
<v Speaker 1>company that makes kool aid fluid? Or like who is

0:19:42.040 --> 0:19:44.000
<v Speaker 1>some company that's like really good at making these like

0:19:44.040 --> 0:19:48.360
<v Speaker 1>infinite bands, Because it just likes.

0:19:46.840 --> 0:19:48.479
<v Speaker 3>Right, yeah, like what are the anyway?

0:19:48.560 --> 0:19:48.760
<v Speaker 4>Right?

0:19:48.920 --> 0:19:50.840
<v Speaker 1>But like right, like you know there's going to be

0:19:50.880 --> 0:19:54.760
<v Speaker 1>some yeah urchiery plate that are like thirty x up.

0:19:54.960 --> 0:19:56.760
<v Speaker 1>But you know, I want to get a sense from

0:19:56.800 --> 0:20:00.879
<v Speaker 1>you of so it's really changed a lot, and I

0:20:01.000 --> 0:20:02.600
<v Speaker 1>kind of you know, in the last several months.

0:20:02.600 --> 0:20:04.080
<v Speaker 3>Could we see it from in video results?

0:20:04.119 --> 0:20:08.040
<v Speaker 1>What you're describing, like how big is the market getting

0:20:08.119 --> 0:20:09.520
<v Speaker 1>and the way I think you know, I know, like

0:20:09.520 --> 0:20:13.040
<v Speaker 1>with AI, there's training and they sort of build the

0:20:13.080 --> 0:20:15.199
<v Speaker 1>model and then there's inference, and the inference is how

0:20:15.240 --> 0:20:17.600
<v Speaker 1>they spit out the results. Can you talk a little

0:20:17.600 --> 0:20:20.920
<v Speaker 1>bit about what you're seeing in terms of the growth

0:20:21.400 --> 0:20:24.760
<v Speaker 1>of both of those aspects of AI, which is bigger

0:20:25.000 --> 0:20:27.240
<v Speaker 1>and which is growing faster? And how do they compare

0:20:27.280 --> 0:20:29.720
<v Speaker 1>to like the size of the installed compute base that

0:20:29.760 --> 0:20:30.440
<v Speaker 1>already exists.

0:20:31.240 --> 0:20:34.760
<v Speaker 4>Oh. Absolutely, So this is one of my favorite topics

0:20:34.800 --> 0:20:37.280
<v Speaker 4>because it's just mind blowing the scale that's going to

0:20:37.280 --> 0:20:41.719
<v Speaker 4>be needed to support AI and scale this infrastructure. So okay,

0:20:41.800 --> 0:20:45.600
<v Speaker 4>so today most of the funding that's going into the

0:20:45.600 --> 0:20:49.800
<v Speaker 4>AI space is too for funding to train next generation

0:20:50.600 --> 0:20:53.400
<v Speaker 4>foundation models. Right, So when a company's raising a bunch

0:20:53.440 --> 0:20:55.119
<v Speaker 4>of money at the end of the day, most of

0:20:55.119 --> 0:20:57.680
<v Speaker 4>that money is going into cloud compute to go train

0:20:57.760 --> 0:21:01.200
<v Speaker 4>this next generation found model to build that intellectual property.

0:21:01.280 --> 0:21:03.360
<v Speaker 4>So they have this model and they can go bring

0:21:03.359 --> 0:21:06.800
<v Speaker 4>it into the inference market. And what I would say is,

0:21:07.280 --> 0:21:12.160
<v Speaker 4>we're having a supply demand issue like a chip access

0:21:12.200 --> 0:21:17.280
<v Speaker 4>crunch in the training phase, where in reality, the scale

0:21:17.440 --> 0:21:20.800
<v Speaker 4>of the inference market is where we're all the demand

0:21:21.000 --> 0:21:24.560
<v Speaker 4>truly is going to sit. So what I'd offer to

0:21:24.600 --> 0:21:28.720
<v Speaker 4>help contextualize that is, let's take you know, there's some

0:21:28.760 --> 0:21:30.880
<v Speaker 4>well known models in the market today. Let's let's say

0:21:30.920 --> 0:21:35.080
<v Speaker 4>there's a preach an in market trained model and it

0:21:35.160 --> 0:21:37.679
<v Speaker 4>took about let's say ten thousand. A one hundred or

0:21:37.680 --> 0:21:39.479
<v Speaker 4>so to train A one hundred is the last generation

0:21:39.560 --> 0:21:41.400
<v Speaker 4>in chip, but you know it still applies in terms

0:21:41.440 --> 0:21:45.520
<v Speaker 4>of relative scale here. So that company that used ten

0:21:46.520 --> 0:21:50.840
<v Speaker 4>train their model, our understanding is they're going to need

0:21:50.880 --> 0:21:55.760
<v Speaker 4>about a million GPUs within one to two years of

0:21:55.840 --> 0:21:59.760
<v Speaker 4>launch to support the entire inference demand.

0:22:00.720 --> 0:22:04.440
<v Speaker 1>So ten you could train the model on ten thousand

0:22:04.440 --> 0:22:06.920
<v Speaker 1>of these chips, ten thousand of these sisters, whatever they're

0:22:07.119 --> 0:22:09.080
<v Speaker 1>and then if they're actually going to be in the

0:22:09.119 --> 0:22:13.160
<v Speaker 1>market and sell something or provide some service to make

0:22:13.160 --> 0:22:13.720
<v Speaker 1>it worthwhile.

0:22:13.720 --> 0:22:15.040
<v Speaker 3>They're going to need a million.

0:22:15.680 --> 0:22:17.960
<v Speaker 4>A million, and I think that's just within first two

0:22:18.000 --> 0:22:21.440
<v Speaker 4>years of launch. Show like we're we're talking about something

0:22:21.440 --> 0:22:25.720
<v Speaker 4>that's going to continue growing afterwards. And so what does

0:22:25.720 --> 0:22:28.439
<v Speaker 4>a million GPUs mean? Obviously? Right, so you know a

0:22:28.440 --> 0:22:31.520
<v Speaker 4>couple I think it was like into last year, all

0:22:31.560 --> 0:22:35.600
<v Speaker 4>the hyperscalers combined, right, Amazon, Google, Microsoft, Oracle. You can

0:22:35.600 --> 0:22:37.479
<v Speaker 4>throw a COORWY from there, it was about, you know,

0:22:37.640 --> 0:22:42.400
<v Speaker 4>five hundred thousand GPUs globally right available across those platforms.

0:22:42.720 --> 0:22:44.760
<v Speaker 4>I'd see it end of this year, it'll be closer

0:22:44.800 --> 0:22:48.720
<v Speaker 4>to a million or so. But that's suggesting then that

0:22:48.920 --> 0:22:53.440
<v Speaker 4>one AI company with one model could consume the entire

0:22:53.520 --> 0:22:58.360
<v Speaker 4>global footprint of GPUs. And and now you start to think, wait,

0:22:58.440 --> 0:23:01.040
<v Speaker 4>aren't there a bunch of other companies training these models

0:23:01.040 --> 0:23:03.760
<v Speaker 4>in market right now? And I leo'ld say, yes, there are.

0:23:03.920 --> 0:23:08.240
<v Speaker 4>So it can imply that there are in the short term,

0:23:08.280 --> 0:23:12.480
<v Speaker 4>the demand of several million GPUs just to support the

0:23:12.680 --> 0:23:17.000
<v Speaker 4>inference market. And there's just there's just nowhere near enough

0:23:17.320 --> 0:23:20.639
<v Speaker 4>globally of this infrastructure, and it's it's going to be

0:23:20.680 --> 0:23:24.119
<v Speaker 4>a big challenge for the market as we exit this

0:23:24.200 --> 0:23:26.800
<v Speaker 4>training phase and move into the productization or really just

0:23:26.840 --> 0:23:29.080
<v Speaker 4>the commercialization of these models, like how do you generate

0:23:29.119 --> 0:23:32.640
<v Speaker 4>revenue off them? And it's it's something that I don't

0:23:32.680 --> 0:23:36.440
<v Speaker 4>think many people truly understand just the amount of scale

0:23:36.520 --> 0:23:39.800
<v Speaker 4>and construction that needs to take place. And now you

0:23:39.840 --> 0:23:42.119
<v Speaker 4>put that in the same framework of the data centers

0:23:42.119 --> 0:23:43.920
<v Speaker 4>that we were talking about, right, So there's this lack

0:23:43.960 --> 0:23:46.280
<v Speaker 4>of data center space, there's lack of chipset supply, like

0:23:46.359 --> 0:23:49.920
<v Speaker 4>it's it's going to be an issue for years that

0:23:49.960 --> 0:23:50.560
<v Speaker 4>we see.

0:23:50.840 --> 0:23:53.800
<v Speaker 2>So when it comes to scale, you know, you keep

0:23:53.840 --> 0:23:57.679
<v Speaker 2>mentioning the hyper scalers, which is a great term, but

0:23:57.960 --> 0:24:02.560
<v Speaker 2>people like Amazon, Google, I guess, Microsoft, IBM, et cetera.

0:24:03.359 --> 0:24:07.560
<v Speaker 2>How quickly or what is your impression of how quickly

0:24:07.880 --> 0:24:11.159
<v Speaker 2>they are able to ramp up in this space? Like

0:24:11.320 --> 0:24:15.200
<v Speaker 2>how fast could they react to some of the trends

0:24:15.240 --> 0:24:16.280
<v Speaker 2>that you've been outlining.

0:24:17.520 --> 0:24:20.600
<v Speaker 4>Yeah, so I can offer what I'm seeing today. You know,

0:24:20.760 --> 0:24:25.159
<v Speaker 4>the h one hundreds started to be distributed globally to

0:24:26.359 --> 0:24:28.720
<v Speaker 4>all of us, right, like all the entities that have

0:24:28.800 --> 0:24:31.439
<v Speaker 4>these you know, kind of upper tier relationships with Nvidia

0:24:31.720 --> 0:24:35.080
<v Speaker 4>back in March, right, so we started getting them the

0:24:35.080 --> 0:24:37.959
<v Speaker 4>s infrastructure online in April, really scaling in May, and

0:24:38.040 --> 0:24:40.160
<v Speaker 4>you know, we have builds going on at ten data

0:24:40.160 --> 0:24:42.719
<v Speaker 4>centers across the US right now, and we're delivering it

0:24:42.720 --> 0:24:46.680
<v Speaker 4>to clients. The guidance that we're seeing from the hyperscalers

0:24:47.240 --> 0:24:50.760
<v Speaker 4>is that they're not going to begin delivering scale access

0:24:51.080 --> 0:24:54.720
<v Speaker 4>to the H one hundred chipset until late Q three,

0:24:55.880 --> 0:24:57.920
<v Speaker 4>maybe mid Q four, and some of them are even

0:24:57.960 --> 0:25:01.159
<v Speaker 4>beginning to guide into Q one. And it's all driven

0:25:01.400 --> 0:25:04.040
<v Speaker 4>by the fact that this is just a different type

0:25:04.040 --> 0:25:07.919
<v Speaker 4>of compute that they're building relative to last generation. Right

0:25:07.920 --> 0:25:10.720
<v Speaker 4>You're no longer just running Ethernet to your point, between

0:25:10.760 --> 0:25:13.360
<v Speaker 4>all these devices, you're not just plugging in CPU blades.

0:25:13.440 --> 0:25:15.720
<v Speaker 4>You're having to deal with like totally different data center

0:25:15.760 --> 0:25:20.240
<v Speaker 4>power density and cooling requirements. You're having to build supercomputers instead,

0:25:20.359 --> 0:25:24.119
<v Speaker 4>with five hundred miles of fiber and all these connections.

0:25:24.119 --> 0:25:26.480
<v Speaker 4>It's just it's a completely different way to build the cloud,

0:25:26.520 --> 0:25:29.760
<v Speaker 4>and it's taking them some time to catch up because

0:25:29.760 --> 0:25:32.159
<v Speaker 4>you have to retrain entire organizations to do this. So

0:25:32.960 --> 0:25:35.399
<v Speaker 4>you know, as of now, i'd say the direct answer

0:25:35.480 --> 0:25:38.920
<v Speaker 4>is three quarters after a chip set launch, But it's

0:25:38.920 --> 0:25:41.760
<v Speaker 4>seeming it might take longer, And I think that's all

0:25:41.760 --> 0:25:45.720
<v Speaker 4>going to contribute to this just kind of slower ability

0:25:45.800 --> 0:25:50.760
<v Speaker 4>to scale infrastructure than what's being dictated by the adoption

0:25:50.920 --> 0:25:53.480
<v Speaker 4>rate of AI software, And it's going to lead to

0:25:53.480 --> 0:25:56.600
<v Speaker 4>this supply demand imbalance that will just last for a while.

0:25:57.640 --> 0:26:00.479
<v Speaker 2>You know, you keep mentioning or we both keep mentioning

0:26:00.520 --> 0:26:03.800
<v Speaker 2>the H one hundred for obvious reasons, But do you

0:26:03.840 --> 0:26:08.199
<v Speaker 2>look at other chips or what would happen to you know,

0:26:08.280 --> 0:26:11.439
<v Speaker 2>your own business if, for instance, a new chip was

0:26:11.480 --> 0:26:14.920
<v Speaker 2>developed that could do the same thing or better than

0:26:15.080 --> 0:26:17.640
<v Speaker 2>an Nvidia H one hundred. Like, for instance, I hear

0:26:17.640 --> 0:26:19.919
<v Speaker 2>a lot of excitement about some of the stuff that

0:26:19.960 --> 0:26:25.040
<v Speaker 2>AMD is developing. And I'm not a chips expert, except

0:26:25.119 --> 0:26:29.159
<v Speaker 2>maybe when it comes to freedo's or layers. But like,

0:26:30.080 --> 0:26:33.840
<v Speaker 2>how how big a difference would that make to you

0:26:34.200 --> 0:26:39.199
<v Speaker 2>if we suddenly got a different chip manufacturer gain prominence

0:26:39.320 --> 0:26:39.720
<v Speaker 2>in AI.

0:26:40.800 --> 0:26:45.520
<v Speaker 4>Sure? So I'd offer kind of two broad responses. One, typically,

0:26:45.720 --> 0:26:50.080
<v Speaker 4>when you train a model you're going to use, you're

0:26:50.119 --> 0:26:52.719
<v Speaker 4>going to use the same chips for inference on that

0:26:52.840 --> 0:26:55.520
<v Speaker 4>model as well. Right, So two PT four, For example,

0:26:55.600 --> 0:26:58.399
<v Speaker 4>I was trained on a one hundreds, they're predominantly going

0:26:58.480 --> 0:27:00.440
<v Speaker 4>to use a one hundreds going for or you might

0:27:00.440 --> 0:27:03.400
<v Speaker 4>fit in some kind of newer generation hyper efficient chips

0:27:03.400 --> 0:27:06.199
<v Speaker 4>into there, but it's not like you need a quote

0:27:07.000 --> 0:27:10.200
<v Speaker 4>a GP with more vram on it, right, Like you're

0:27:10.240 --> 0:27:12.439
<v Speaker 4>in a need your forty gig or your your eighty

0:27:12.480 --> 0:27:15.879
<v Speaker 4>grid gig ram chip because that's the size of the

0:27:15.880 --> 0:27:18.200
<v Speaker 4>model that that you trained, Right, You're not gonna need

0:27:18.280 --> 0:27:20.680
<v Speaker 4>like next multiple generations. You're not going to like really

0:27:20.680 --> 0:27:23.479
<v Speaker 4>be able to adopt them to change the efficiency of

0:27:23.760 --> 0:27:26.480
<v Speaker 4>serving that model. So what we view is that a

0:27:26.560 --> 0:27:30.560
<v Speaker 4>chip's lifespan is like this first two to three years

0:27:30.800 --> 0:27:34.240
<v Speaker 4>is spent training models, and then it's next four to

0:27:34.359 --> 0:27:38.480
<v Speaker 4>five years is spent doing inference for those models that

0:27:38.560 --> 0:27:42.159
<v Speaker 4>it trained. And then within there as well, you do

0:27:42.200 --> 0:27:44.879
<v Speaker 4>this thing called fine tuning, which is updating the model

0:27:44.960 --> 0:27:47.199
<v Speaker 4>with new information, right, Like how do you keep a

0:27:47.200 --> 0:27:49.560
<v Speaker 4>model like up to date with what's happened on a

0:27:49.600 --> 0:27:53.399
<v Speaker 4>Twitter or what's happened on in the media. Right, you

0:27:53.480 --> 0:27:55.680
<v Speaker 4>have to keep retraining it, right, and you'll use those

0:27:55.680 --> 0:27:58.080
<v Speaker 4>same chips to do that. But so your question on

0:27:58.240 --> 0:28:01.000
<v Speaker 4>other chip sets, and this is something that we have

0:28:01.040 --> 0:28:05.000
<v Speaker 4>a particularly interesting view into because we have like you know,

0:28:05.080 --> 0:28:07.720
<v Speaker 4>call it six hundred and fifty AI clients right, and

0:28:07.760 --> 0:28:10.960
<v Speaker 4>we're having conversations with them daily to ensure that we're

0:28:11.000 --> 0:28:13.960
<v Speaker 4>meeting their scaling demands. So it gives us a look

0:28:13.960 --> 0:28:17.480
<v Speaker 4>into six to twelve months into the future what type

0:28:17.480 --> 0:28:21.480
<v Speaker 4>of infrastructure they expect to need, and it's it's overwhelmingly

0:28:21.840 --> 0:28:26.479
<v Speaker 4>people still want access to Nvidia chips and the reason

0:28:26.560 --> 0:28:29.320
<v Speaker 4>for this is something that dates back, I think it's

0:28:29.359 --> 0:28:34.000
<v Speaker 4>nearly fifteen years when Nvidia and Jensen made the decision

0:28:34.040 --> 0:28:38.400
<v Speaker 4>to open source Kuda and to make this software set

0:28:38.600 --> 0:28:42.840
<v Speaker 4>accessible to the machine learning community. And you know today

0:28:42.840 --> 0:28:44.640
<v Speaker 4>if you go to GitHub and you search a machine

0:28:44.680 --> 0:28:49.200
<v Speaker 4>learning project, they's all reference Kuda drivers. And he's established

0:28:49.200 --> 0:28:55.320
<v Speaker 4>this utter dominance of ecosystem around his compute within the

0:28:55.440 --> 0:28:58.640
<v Speaker 4>mL space really similar to like the x eighty six

0:28:58.840 --> 0:29:02.360
<v Speaker 4>instruction set for CP you versus ARM, right, like X

0:29:02.400 --> 0:29:04.880
<v Speaker 4>eighty six is is used prodominantly. ARM has been trying

0:29:04.880 --> 0:29:07.400
<v Speaker 4>to find its way into the space for a while

0:29:07.480 --> 0:29:10.360
<v Speaker 4>now and it's just really struggled because all the engineers

0:29:10.360 --> 0:29:13.680
<v Speaker 4>and developers are used to x eighty six. Similar to

0:29:13.800 --> 0:29:16.520
<v Speaker 4>how all the engineers and developers in the AI space

0:29:16.600 --> 0:29:20.280
<v Speaker 4>are used to using KUDA, so it's something that like

0:29:20.360 --> 0:29:25.320
<v Speaker 4>obviously AMD is highly incentivized to find a way into

0:29:25.360 --> 0:29:28.480
<v Speaker 4>the sector, but they just don't have the ecosystem and

0:29:28.520 --> 0:29:30.760
<v Speaker 4>it's a huge moat to deal with. Then, you know,

0:29:30.880 --> 0:29:35.280
<v Speaker 4>kudos to Nvidia for establishing themselves and having the patients

0:29:35.320 --> 0:29:37.720
<v Speaker 4>to stick with it and to continue to support that

0:29:37.760 --> 0:29:40.120
<v Speaker 4>community over the last fifteen years, and it's it's really

0:29:40.120 --> 0:29:43.040
<v Speaker 4>paying off for them in spades today. You know, if

0:29:43.080 --> 0:29:46.560
<v Speaker 4>the demand comes for that infrastructure at some point, it's

0:29:46.680 --> 0:29:49.960
<v Speaker 4>you know, we can run other pieces of infrastructure within

0:29:50.000 --> 0:29:54.000
<v Speaker 4>our data center. But I also find that Nvidia has

0:29:54.080 --> 0:29:57.440
<v Speaker 4>such an advantage on the competition with not only its GPUs,

0:29:57.480 --> 0:30:00.600
<v Speaker 4>but all its components that support the gp USE, like

0:30:00.760 --> 0:30:04.400
<v Speaker 4>the infinite band fabric, that it's it's gonna be a

0:30:04.440 --> 0:30:08.320
<v Speaker 4>really difficult company to displace from the market in terms

0:30:08.360 --> 0:30:12.280
<v Speaker 4>of the best standard for AI infrastructure.

0:30:12.840 --> 0:30:14.680
<v Speaker 1>Can I ask a question, and I'm gonna I want

0:30:14.680 --> 0:30:17.000
<v Speaker 1>to ask this politely because it's not intended to be

0:30:17.120 --> 0:30:20.560
<v Speaker 1>accusatory or anything like that, So I don't want you

0:30:20.560 --> 0:30:22.840
<v Speaker 1>to you know here it is like but like when

0:30:22.840 --> 0:30:29.200
<v Speaker 1>you're like talking about like hyperscalers and you're like you know, Amazon, Google, Microsoft,

0:30:29.200 --> 0:30:31.000
<v Speaker 1>and you know kind of core Weave, and it's like, okay,

0:30:31.000 --> 0:30:33.640
<v Speaker 1>those are trillion dollar companies and you're a two billion

0:30:33.680 --> 0:30:36.760
<v Speaker 1>dollar company. Like why like I don't still don't think

0:30:36.800 --> 0:30:38.560
<v Speaker 1>I like wrap my head around, like and I know,

0:30:38.640 --> 0:30:41.000
<v Speaker 1>like they're all like in they're all talking about.

0:30:40.760 --> 0:30:41.520
<v Speaker 3>AI et cetera.

0:30:41.600 --> 0:30:43.360
<v Speaker 1>Like can you still just like explain to me a

0:30:43.400 --> 0:30:46.080
<v Speaker 1>little bit, like why aren't they just gonna frankly like

0:30:46.200 --> 0:30:49.080
<v Speaker 1>steamroll you or be able to let's put it this way,

0:30:49.360 --> 0:30:52.160
<v Speaker 1>be able to Okay, maybe it'll take a few quarters

0:30:52.200 --> 0:30:55.840
<v Speaker 1>to re evaluate things, but like you know, eventually this

0:30:56.040 --> 0:30:59.360
<v Speaker 1>just becomes this sort of de facto offering from these

0:30:59.400 --> 0:31:02.960
<v Speaker 1>big is that have these huge cloud budgets that must

0:31:02.960 --> 0:31:05.680
<v Speaker 1>be orders of magnitude large larger than yours.

0:31:06.320 --> 0:31:08.120
<v Speaker 4>Yeah. Yeah, I would really love to be able to

0:31:08.160 --> 0:31:11.040
<v Speaker 4>have access to their their cost of capital, that's pretty sure.

0:31:12.120 --> 0:31:15.480
<v Speaker 4>So the way, look, it's the way I had to talk

0:31:15.480 --> 0:31:18.960
<v Speaker 4>about this is we don't have a silver bullet necessarily, right.

0:31:18.960 --> 0:31:21.600
<v Speaker 4>I can't point to like a super secret piece of

0:31:21.640 --> 0:31:24.400
<v Speaker 4>technology that we put inside of our servers or anything

0:31:24.400 --> 0:31:27.680
<v Speaker 4>along those lines. But the way I like to broadly contextualize,

0:31:27.680 --> 0:31:33.680
<v Speaker 4>it is referencing another sector, and it's that like Ford

0:31:34.080 --> 0:31:37.000
<v Speaker 4>should be able to produce a model, why right, Like

0:31:37.240 --> 0:31:39.280
<v Speaker 4>they have the budget, they have the people, they have

0:31:39.400 --> 0:31:43.920
<v Speaker 4>the decades of expertise. But in order to ask them

0:31:43.920 --> 0:31:46.320
<v Speaker 4>to produce a model, why you would have to ask

0:31:46.360 --> 0:31:50.560
<v Speaker 4>them to foundationally change the way that they produce a vehicle,

0:31:50.880 --> 0:31:55.280
<v Speaker 4>all the way from research to servicing and that entire mechanism.

0:31:55.680 --> 0:31:58.120
<v Speaker 4>Like it's a giant organization. Now you have to go

0:31:58.200 --> 0:32:01.240
<v Speaker 4>ask that huge organization and people to change the way

0:32:01.240 --> 0:32:03.960
<v Speaker 4>that they go about producing things.

0:32:04.000 --> 0:32:05.560
<v Speaker 1>And I get that, but just to push back a

0:32:05.600 --> 0:32:07.280
<v Speaker 1>little bit, and I get And this is like a

0:32:07.280 --> 0:32:10.000
<v Speaker 1>theme that we that comes up in various flavors on

0:32:10.120 --> 0:32:12.800
<v Speaker 1>odd lots a lot, which is that like companies have

0:32:13.000 --> 0:32:16.600
<v Speaker 1>internal it's really hard to replicate sort of like tacit

0:32:16.720 --> 0:32:20.280
<v Speaker 1>knowledge within a corporation. And we see that with companies

0:32:20.280 --> 0:32:22.680
<v Speaker 1>that make semiconductor equipment. We see that with companies that

0:32:22.720 --> 0:32:25.840
<v Speaker 1>make airplanes. We see that with real estate developers that

0:32:26.040 --> 0:32:28.479
<v Speaker 1>know how to turn an office building into a condo.

0:32:28.520 --> 0:32:30.479
<v Speaker 1>And so I think this is like a deep point,

0:32:31.200 --> 0:32:34.000
<v Speaker 1>but you know they are offering AI stuff like I

0:32:34.000 --> 0:32:36.800
<v Speaker 1>can look at Google right now, like there's Cloud AI

0:32:37.160 --> 0:32:39.600
<v Speaker 1>like and there's Asia AI, and they all have their announcements.

0:32:39.680 --> 0:32:41.480
<v Speaker 1>So I'm still trying to understand, like what is it

0:32:42.080 --> 0:32:45.120
<v Speaker 1>that you're offering that all the hyper scalers they all have,

0:32:45.240 --> 0:32:47.680
<v Speaker 1>they all say they have AI offering, So what is

0:32:47.720 --> 0:32:49.920
<v Speaker 1>the difference between sort of like what you have and

0:32:50.000 --> 0:32:52.920
<v Speaker 1>what they say is like their you know, AI compute platforms.

0:32:54.000 --> 0:32:56.320
<v Speaker 4>Absolutely, and this will really depend on how much technical

0:32:56.360 --> 0:32:59.360
<v Speaker 4>detail you like me to get into. But broadly, through

0:33:00.120 --> 0:33:03.960
<v Speaker 4>structure differentiation like literally using different components to build our cloud,

0:33:04.360 --> 0:33:07.520
<v Speaker 4>and through software differentiation we use different pieces of software

0:33:07.560 --> 0:33:11.400
<v Speaker 4>to operate and optimize our cloud, we're able to deliver

0:33:11.480 --> 0:33:15.240
<v Speaker 4>a product that's about forty to sixty percent more efficient

0:33:15.600 --> 0:33:18.000
<v Speaker 4>on a workload adjusted basis than what you find across

0:33:18.040 --> 0:33:21.440
<v Speaker 4>any of the hyperscalers. So, in other words, if you

0:33:21.440 --> 0:33:23.560
<v Speaker 4>were to take the same workload or like go do

0:33:23.680 --> 0:33:27.880
<v Speaker 4>the same process at a hyperscaler on the exact same

0:33:28.240 --> 0:33:32.360
<v Speaker 4>GPU compute versus core weave, we're going to be forty

0:33:32.360 --> 0:33:36.040
<v Speaker 4>to sixty percent more efficient at doing that because of

0:33:36.040 --> 0:33:39.520
<v Speaker 4>the way that we've configured everything relative to the hyperscalers

0:33:39.520 --> 0:33:43.040
<v Speaker 4>and it comes back to this analogy between like why

0:33:43.080 --> 0:33:45.960
<v Speaker 4>Forward can't produce the model? Why again like they can.

0:33:46.120 --> 0:33:49.320
<v Speaker 4>These are trillion dollar companies we're talking about. To your point,

0:33:49.320 --> 0:33:51.160
<v Speaker 4>they have the budget, they have the personnel, and they

0:33:51.200 --> 0:33:54.200
<v Speaker 4>certainly have the motivation to do so. But you know,

0:33:54.280 --> 0:33:57.280
<v Speaker 4>it's not just one singular thing they have to change.

0:33:57.280 --> 0:34:01.040
<v Speaker 4>It's a completely different way to building their their business

0:34:01.200 --> 0:34:04.440
<v Speaker 4>that they would have to orchestrate. And it's what's the analogies.

0:34:04.760 --> 0:34:07.520
<v Speaker 4>However many miles it takes to turn an aircraft carrier, right,

0:34:07.560 --> 0:34:09.279
<v Speaker 4>like it's it's going to take them a while to

0:34:09.320 --> 0:34:12.160
<v Speaker 4>do that. And I think if they do get there

0:34:12.400 --> 0:34:14.799
<v Speaker 4>at some point, which you know, I don't disagree with you,

0:34:14.920 --> 0:34:18.200
<v Speaker 4>they're certainly motivated to, it's it's going to have taken

0:34:18.239 --> 0:34:20.960
<v Speaker 4>them some time, literally years to get there, and they're

0:34:21.000 --> 0:34:23.839
<v Speaker 4>going to look really similar to us. And meanwhile, I've

0:34:24.280 --> 0:34:27.640
<v Speaker 4>dominated mortgage share and I've really established my product and

0:34:27.719 --> 0:34:30.440
<v Speaker 4>market and I continue when I'll continue to differentiate myself

0:34:30.480 --> 0:34:32.160
<v Speaker 4>on the software asign business as well.

0:34:49.120 --> 0:34:52.760
<v Speaker 2>Since we're on the topic of adaptation, can I ask about,

0:34:53.239 --> 0:34:56.319
<v Speaker 2>you know, your own evolution as a company, because I

0:34:56.360 --> 0:35:00.160
<v Speaker 2>think I've read that you started out in ethereum mining,

0:35:00.320 --> 0:35:03.719
<v Speaker 2>and at one point I'm pretty sure crypto mining was

0:35:03.800 --> 0:35:07.520
<v Speaker 2>a substantial, if not the biggest, portion of your business.

0:35:08.000 --> 0:35:14.000
<v Speaker 2>But you have clearly adapted or pivoted into this AI space.

0:35:14.080 --> 0:35:16.200
<v Speaker 2>So what has that been like and can you maybe

0:35:16.239 --> 0:35:20.040
<v Speaker 2>describe some of the trends that you've seen over your history.

0:35:21.160 --> 0:35:24.319
<v Speaker 4>Yes, absolutely, and you're right. We did start within the

0:35:24.320 --> 0:35:28.080
<v Speaker 4>cryptocurrency space back in twenty seventeen or so, and that

0:35:28.280 --> 0:35:32.279
<v Speaker 4>was spawned out of just frankly curiosity from a group

0:35:32.320 --> 0:35:36.640
<v Speaker 4>of former commodity traders. So myself, my two co founders,

0:35:36.840 --> 0:35:39.920
<v Speaker 4>we ran hedge funds, we ran family offices, so we

0:35:40.000 --> 0:35:42.480
<v Speaker 4>traded in these energy markets. So we were always attracted

0:35:42.520 --> 0:35:45.520
<v Speaker 4>to supply demand mechanics. But what attracted us but then

0:35:45.560 --> 0:35:49.800
<v Speaker 4>cryptocurrency was there's this arbitrage opportunity that was a permissionless

0:35:49.920 --> 0:35:52.400
<v Speaker 4>revenue stream, right, Like I knew the cost of power,

0:35:52.800 --> 0:35:55.239
<v Speaker 4>I knew what the hardware could generate in terms of

0:35:55.280 --> 0:35:58.719
<v Speaker 4>revenue with using a power input. Thus it's effectively an

0:35:58.800 --> 0:36:02.880
<v Speaker 4>arbitrage right, So we explored that we had some of

0:36:02.880 --> 0:36:06.359
<v Speaker 4>the infrastructure operating literally in our basements. As you said,

0:36:09.200 --> 0:36:12.720
<v Speaker 4>then that like quickly turned into scaling across warehouses, and

0:36:13.160 --> 0:36:16.520
<v Speaker 4>at some point in twenty I think it was twenty eighteen,

0:36:16.640 --> 0:36:21.560
<v Speaker 4>maybe late twenty eighteen, we were the largest ethereum miner

0:36:21.880 --> 0:36:26.160
<v Speaker 4>in North America. We were operating over fifty thousand GPUs,

0:36:26.200 --> 0:36:29.880
<v Speaker 4>we represented over one percent of the ethereum network. But

0:36:31.040 --> 0:36:33.400
<v Speaker 4>during that whole time, we just kept coming back to

0:36:33.440 --> 0:36:37.400
<v Speaker 4>the idea that there's no moat, there's no advantage that

0:36:37.840 --> 0:36:41.680
<v Speaker 4>we could create for ourselves relative to our competitors, right, Like, sure,

0:36:41.680 --> 0:36:44.160
<v Speaker 4>you could maybe focus on power price and just kind

0:36:44.200 --> 0:36:46.480
<v Speaker 4>of chase the cheapest power, but that just felt like

0:36:46.560 --> 0:36:49.080
<v Speaker 4>chasing to the bottom of the bucket, right. You know,

0:36:49.560 --> 0:36:51.200
<v Speaker 4>I think an area we could have gone into is

0:36:51.200 --> 0:36:53.640
<v Speaker 4>producing your own chips, right because if you produce the

0:36:53.640 --> 0:36:56.359
<v Speaker 4>own chips and you run the mining equipment before anyone

0:36:56.400 --> 0:36:58.920
<v Speaker 4>else has access to it, then you have an advantage

0:36:58.920 --> 0:37:00.719
<v Speaker 4>for that period. But you know, we weren't going to

0:37:00.719 --> 0:37:04.200
<v Speaker 4>go design and fabric own chips. So what we kept

0:37:04.239 --> 0:37:08.440
<v Speaker 4>coming back to was this GPU compute, Man, what if

0:37:08.480 --> 0:37:10.520
<v Speaker 4>we could do other things, right, like what if they

0:37:10.560 --> 0:37:15.240
<v Speaker 4>were what if we could develop uncorrelated optionality into multiple

0:37:15.320 --> 0:37:19.200
<v Speaker 4>high growth markets right in those markets or where we

0:37:19.440 --> 0:37:22.760
<v Speaker 4>predominantly sit today with an artificial intelligence, media and entertainment,

0:37:22.800 --> 0:37:27.040
<v Speaker 4>and computational chemistry. And the original thesis was, well, whenever

0:37:27.040 --> 0:37:31.360
<v Speaker 4>our compute isn't being allocated into those sectors, we'll just

0:37:31.400 --> 0:37:34.280
<v Speaker 4>have it mining cryptocurrency and we'll build out this fantastic

0:37:34.320 --> 0:37:37.279
<v Speaker 4>company that has one hundred percent utilization rate across the

0:37:37.280 --> 0:37:40.920
<v Speaker 4>infrastructure because it could switch immediately from being released from

0:37:40.960 --> 0:37:43.600
<v Speaker 4>an AI workload into going back into the Ethereum network.

0:37:44.360 --> 0:37:47.319
<v Speaker 4>And we did get a brief glimpse of being able

0:37:47.360 --> 0:37:51.440
<v Speaker 4>to operate that way in twenty twenty one, as we

0:37:51.560 --> 0:37:55.320
<v Speaker 4>had our cloud live and we had AI clients in place,

0:37:55.640 --> 0:37:59.880
<v Speaker 4>but Ethereum mining effectively ended during the merge in Q

0:38:00.200 --> 0:38:04.480
<v Speaker 4>three of twenty twenty two. But I'd say the other

0:38:04.560 --> 0:38:10.239
<v Speaker 4>thing that we never appreciated was the utter complexity of

0:38:10.320 --> 0:38:14.760
<v Speaker 4>running a CSP forgetting about the software side of the business,

0:38:14.760 --> 0:38:16.680
<v Speaker 4>which in and of itself, you know, we spent about

0:38:16.719 --> 0:38:20.320
<v Speaker 4>four years developing the software to build a modern cloud

0:38:20.360 --> 0:38:23.600
<v Speaker 4>to do infrastructure orchestration and actually be a cloud service provider.

0:38:24.200 --> 0:38:29.400
<v Speaker 4>The components themselves that the sector broadly used for crypto

0:38:29.480 --> 0:38:33.920
<v Speaker 4>mining were these retail grade GPUs, right, the kind of

0:38:33.960 --> 0:38:37.359
<v Speaker 4>things that you plug in your desktop to go play video.

0:38:37.600 --> 0:38:41.040
<v Speaker 3>They were like selling them on stock X. Yes, yes

0:38:41.480 --> 0:38:41.719
<v Speaker 3>it was.

0:38:41.760 --> 0:38:44.080
<v Speaker 4>It was crazy during that period to get your hands

0:38:44.080 --> 0:38:45.839
<v Speaker 4>on that infrastructure for crypto.

0:38:45.560 --> 0:38:48.560
<v Speaker 1>Mining, and all the video gamers hated the crypto people,

0:38:48.640 --> 0:38:50.319
<v Speaker 1>right because they're like, I want to like play this

0:38:50.400 --> 0:38:52.320
<v Speaker 1>game and they would like line up what is it?

0:38:52.920 --> 0:38:55.239
<v Speaker 1>Game stop and like the geek wire shop and all

0:38:55.280 --> 0:38:57.560
<v Speaker 1>that or whatever it is, and they like couldn't get

0:38:57.560 --> 0:38:58.759
<v Speaker 1>it because you got it, not you.

0:38:58.920 --> 0:39:01.359
<v Speaker 3>But yeah, they're orbating.

0:39:01.040 --> 0:39:03.319
<v Speaker 1>Access to the chips first and getting more value out

0:39:03.360 --> 0:39:04.520
<v Speaker 1>of them so that you could bit them up.

0:39:05.440 --> 0:39:08.920
<v Speaker 4>We were certainly part of the problem, and that's absolutely correct.

0:39:09.600 --> 0:39:12.640
<v Speaker 4>But you know what we found ultimately is like those chips,

0:39:13.560 --> 0:39:16.479
<v Speaker 4>that's not what you run enterprise grade workloads on. That's

0:39:16.520 --> 0:39:19.319
<v Speaker 4>not what's supporting you know, the largest AI companies in

0:39:19.360 --> 0:39:23.240
<v Speaker 4>the world, And starting in twenty nineteen, we stopped buying

0:39:23.400 --> 0:39:27.160
<v Speaker 4>any of those chips and only focused on purchasing enterprise

0:39:27.200 --> 0:39:30.960
<v Speaker 4>grade GPU chip sets that you know, Nvidia has a

0:39:31.000 --> 0:39:34.200
<v Speaker 4>probably about twelve different SKUs that they offer, including a

0:39:34.360 --> 0:39:38.440
<v Speaker 4>one hundred and h one hundred chips, and really oriented

0:39:38.440 --> 0:39:42.200
<v Speaker 4>our business around it. So it's a. I don't expect

0:39:42.320 --> 0:39:46.760
<v Speaker 4>to see much repurposing of this kind of older retail

0:39:46.880 --> 0:39:49.640
<v Speaker 4>grade GPU equipment that was used for crypto mining, because

0:39:50.360 --> 0:39:52.200
<v Speaker 4>in crypto mining, you want to buy the cheapest chip

0:39:52.239 --> 0:39:54.480
<v Speaker 4>that can do the thing for it, right, that can

0:39:54.520 --> 0:39:57.960
<v Speaker 4>participate in crypto mining. But there's a huge difference in

0:39:58.040 --> 0:40:00.880
<v Speaker 4>price between a retail plugin into your computer so you

0:40:00.880 --> 0:40:03.840
<v Speaker 4>can play video games chip and an enterprise grade you

0:40:03.880 --> 0:40:05.680
<v Speaker 4>can run it twenty four to seven. There's not going

0:40:05.719 --> 0:40:07.680
<v Speaker 4>to be downtime, You're going to have a low failure rate.

0:40:08.040 --> 0:40:10.640
<v Speaker 4>Like there's a large technology difference and there's a large

0:40:10.640 --> 0:40:13.840
<v Speaker 4>pricing difference between those and the crypto miners. You only

0:40:13.960 --> 0:40:16.360
<v Speaker 4>needed the retail grade ship because you know, if it

0:40:16.400 --> 0:40:19.239
<v Speaker 4>went down for two percent five percent of the time

0:40:19.280 --> 0:40:21.759
<v Speaker 4>for a failure rate, that's not a big deal. But

0:40:22.080 --> 0:40:27.200
<v Speaker 4>the tolerance, the uptime tolerance for these enterprise grade workloads

0:40:27.320 --> 0:40:30.719
<v Speaker 4>is measured on the thousandths of a percent, and it's

0:40:30.760 --> 0:40:33.960
<v Speaker 4>a different type of infrastructure, so we don't expect to

0:40:34.000 --> 0:40:38.040
<v Speaker 4>see the components really being reused, if at all. And

0:40:38.080 --> 0:40:40.640
<v Speaker 4>then the other variable, going back to the very beginning

0:40:40.640 --> 0:40:43.120
<v Speaker 4>of our conversation are the data centers in which these

0:40:43.120 --> 0:40:47.319
<v Speaker 4>are housed. So Joe, to your point earlier, you know,

0:40:47.400 --> 0:40:49.840
<v Speaker 4>we sit within tier three tier four data centers, and

0:40:49.880 --> 0:40:53.080
<v Speaker 4>that's the basically the broad industry standard for being able

0:40:53.080 --> 0:40:57.560
<v Speaker 4>to serve these kind of workloads. The crypto miners sat

0:40:57.600 --> 0:41:01.399
<v Speaker 4>within tier zero tier one data centers, and these things

0:41:01.440 --> 0:41:05.200
<v Speaker 4>are like highly interruptible. They do like really interesting things

0:41:05.280 --> 0:41:09.040
<v Speaker 4>like helping load balance the power markets in places like

0:41:09.080 --> 0:41:11.520
<v Speaker 4>ir Cot right, Like they'll shut down when power prices

0:41:11.560 --> 0:41:13.840
<v Speaker 4>go too high and it load balances the grid. But

0:41:14.960 --> 0:41:19.000
<v Speaker 4>enterprise AI workloads don't have a tolerance for that. Their

0:41:19.080 --> 0:41:22.200
<v Speaker 4>tolerance again is measured on the thousands of a percentage

0:41:22.239 --> 0:41:26.280
<v Speaker 4>in terms of uptime. So not only does the infrastructure

0:41:26.680 --> 0:41:30.839
<v Speaker 4>not work from cryptomning, but the data centers that they

0:41:31.040 --> 0:41:35.960
<v Speaker 4>built within don't work either the way that they're currently configured. Now,

0:41:36.360 --> 0:41:39.680
<v Speaker 4>they could potentially convert their sites into tier three and

0:41:39.719 --> 0:41:42.279
<v Speaker 4>tier four data centers. I'll tell you that in and

0:41:42.320 --> 0:41:46.200
<v Speaker 4>of itself, that is an extremely challenging task and it

0:41:46.200 --> 0:41:49.840
<v Speaker 4>takes a lot of proprietary knowledge and industry expertise to

0:41:49.880 --> 0:41:51.719
<v Speaker 4>do so. It's not just throwing a few fans in

0:41:51.760 --> 0:41:54.279
<v Speaker 4>a room and a few air conditioning units. It's a

0:41:55.320 --> 0:41:57.840
<v Speaker 4>it's it. Honestly, it feels like walking to a spaceship.

0:41:57.960 --> 0:41:59.960
<v Speaker 3>Tracy, this is this is an episode.

0:42:00.360 --> 0:42:02.560
<v Speaker 1>I don't know about you, Tracy, there's like six another

0:42:02.840 --> 0:42:06.279
<v Speaker 1>like six follow on episodes. No, seriously, like the whole

0:42:06.280 --> 0:42:10.400
<v Speaker 1>like data center market and the coolant and all, you know,

0:42:10.440 --> 0:42:13.600
<v Speaker 1>the electricity, Like there's so many different rabbit holes you

0:42:13.640 --> 0:42:15.960
<v Speaker 1>could go down, just like with the infrastructure you're.

0:42:15.800 --> 0:42:18.920
<v Speaker 2>Talking about, for sure, And I think the estimates that

0:42:19.000 --> 0:42:23.839
<v Speaker 2>I've seen on repurposing crypto GPUs, I think I've seen

0:42:23.880 --> 0:42:28.400
<v Speaker 2>like five to fifteen percent, so to Brannon's point, but

0:42:28.680 --> 0:42:31.000
<v Speaker 2>I'm sure, I'm sure there will be people out there

0:42:31.040 --> 0:42:31.600
<v Speaker 2>who try.

0:42:32.680 --> 0:42:35.560
<v Speaker 4>You got to try, right, because what if it works right,

0:42:35.960 --> 0:42:38.919
<v Speaker 4>If you can make that work, that's amazing. But we're

0:42:39.080 --> 0:42:41.920
<v Speaker 4>just you know, coming as an entity that was an

0:42:41.920 --> 0:42:45.759
<v Speaker 4>extremely large operator of that infrastructure and has built, you know,

0:42:45.880 --> 0:42:48.920
<v Speaker 4>one of the largest cloud service providers for AI workloads.

0:42:49.719 --> 0:42:51.959
<v Speaker 4>I can tell you it's it's gonna be really really

0:42:52.000 --> 0:42:54.239
<v Speaker 4>hard to do it because we've had exposure in both

0:42:54.280 --> 0:42:56.160
<v Speaker 4>those places and at the end of the day, they're

0:42:56.200 --> 0:42:59.719
<v Speaker 4>just very very different businesses, both from the type of

0:43:00.080 --> 0:43:02.400
<v Speaker 4>nearing and developers that you employed to the infrastructure to

0:43:02.440 --> 0:43:03.719
<v Speaker 4>the data centers that you sit within.

0:43:04.920 --> 0:43:07.160
<v Speaker 1>So can I just go back you know, yeah, just

0:43:07.239 --> 0:43:09.680
<v Speaker 1>sort of like big picture, and I guess it sort

0:43:09.680 --> 0:43:11.920
<v Speaker 1>of goes back to like who gets access to what?

0:43:12.000 --> 0:43:14.040
<v Speaker 3>Who gets access to chips?

0:43:14.080 --> 0:43:17.279
<v Speaker 1>And I imagine that you know, not only do you

0:43:17.320 --> 0:43:19.440
<v Speaker 1>need a lot of money to like build a relationship

0:43:19.520 --> 0:43:22.680
<v Speaker 1>with like Nvidio, you also probably need like a you know,

0:43:23.040 --> 0:43:25.399
<v Speaker 1>expectation you're going to be back the next year, back

0:43:25.440 --> 0:43:26.920
<v Speaker 1>the next year, back the next year, and that you

0:43:26.960 --> 0:43:30.040
<v Speaker 1>actually like have relationship and so forth. But I have

0:43:30.080 --> 0:43:33.200
<v Speaker 1>to imagine like planning is really tough, and when like

0:43:33.280 --> 0:43:35.880
<v Speaker 1>you know, you have this sort of like AI Machine

0:43:35.920 --> 0:43:39.960
<v Speaker 1>language whatever like industry, and then something like chet GPT

0:43:40.200 --> 0:43:43.040
<v Speaker 1>comes out and like suddenly everyone like, oh I need

0:43:43.080 --> 0:43:45.600
<v Speaker 1>to like have AI access. Talk to us about like

0:43:45.640 --> 0:43:47.759
<v Speaker 1>the sort of like challenge of just sort of like

0:43:48.120 --> 0:43:51.879
<v Speaker 1>planning to build when it can move that fast, and

0:43:51.960 --> 0:43:54.560
<v Speaker 1>like everyone is just sort of guessing how big this

0:43:54.640 --> 0:43:56.359
<v Speaker 1>market is going to be in two to three years.

0:43:57.080 --> 0:44:00.960
<v Speaker 4>Oh my gosh, it's it's it's been utterly insane right

0:44:01.040 --> 0:44:04.080
<v Speaker 4>like the it you know, back to last year, you know,

0:44:04.120 --> 0:44:06.200
<v Speaker 4>the supply chain and the ability to get your hands

0:44:06.200 --> 0:44:08.640
<v Speaker 4>on components. You know, you would call your your OEM.

0:44:08.960 --> 0:44:12.160
<v Speaker 4>The OEM is the original equipment manufacturer, Like those are

0:44:12.160 --> 0:44:14.760
<v Speaker 4>the super micros, the gigabytes of the world, who actually

0:44:14.840 --> 0:44:17.200
<v Speaker 4>you know, build the nodes, build the servers, and you're

0:44:17.360 --> 0:44:20.040
<v Speaker 4>you're buying through them, and then they buy the GPUs

0:44:20.080 --> 0:44:23.239
<v Speaker 4>from Nvidia and build all the components together. Right, So

0:44:23.480 --> 0:44:25.160
<v Speaker 4>if you called them and said, hey, I need this

0:44:25.239 --> 0:44:29.880
<v Speaker 4>many nodes to be delivered, they'll say, great, we'll start assembling.

0:44:30.040 --> 0:44:32.360
<v Speaker 4>Takes us, you know, a week to two weeks to

0:44:32.360 --> 0:44:34.399
<v Speaker 4>get the parts in assembling, and then it's another week

0:44:34.440 --> 0:44:36.160
<v Speaker 4>for them to ship them to you, and then it

0:44:36.160 --> 0:44:37.880
<v Speaker 4>takes us two to three weeks to plug them in

0:44:37.880 --> 0:44:40.799
<v Speaker 4>and put them online get them going. Right now, that's

0:44:40.920 --> 0:44:45.040
<v Speaker 4>completely changed, as you know, like all the supply chain

0:44:45.040 --> 0:44:48.000
<v Speaker 4>has gotten thrown off so much so that you know,

0:44:48.080 --> 0:44:52.480
<v Speaker 4>in Vidia is fully allocated, like they've fully sold out

0:44:52.480 --> 0:44:56.160
<v Speaker 4>their infrastructure through the end of the year. Right, you

0:44:56.200 --> 0:44:58.319
<v Speaker 4>can't call them, You can't call the OEM and just

0:44:58.320 --> 0:45:01.000
<v Speaker 4>say you need more compute chips like that, that's not possible.

0:45:01.160 --> 0:45:03.560
<v Speaker 4>So much so that you know, when clients are coming

0:45:03.640 --> 0:45:06.279
<v Speaker 4>to us today and they're asking for like a four

0:45:06.320 --> 0:45:09.560
<v Speaker 4>thousand GPU cluster to be built for them. We're telling

0:45:09.560 --> 0:45:12.879
<v Speaker 4>them Q one, and increasingly it's moving towards Q two

0:45:12.880 --> 0:45:14.760
<v Speaker 4>at this point because Q one is starting to get

0:45:15.160 --> 0:45:18.160
<v Speaker 4>booked up right now, So it's something that a lot

0:45:18.200 --> 0:45:20.879
<v Speaker 4>of time has been added to it. And then there's

0:45:20.920 --> 0:45:25.080
<v Speaker 4>other supply chain variables within there as well. You know,

0:45:25.120 --> 0:45:28.520
<v Speaker 4>we had a client earlier this year that we were

0:45:28.520 --> 0:45:30.560
<v Speaker 4>in negotiations with them on the contract and you know,

0:45:30.680 --> 0:45:33.600
<v Speaker 4>we really wanted to perform well on timing for it.

0:45:34.200 --> 0:45:38.080
<v Speaker 4>So we knew because of our orientation within the supply

0:45:38.160 --> 0:45:41.400
<v Speaker 4>chain that there were some critical components that needed to

0:45:41.400 --> 0:45:44.800
<v Speaker 4>be ordered ahead of time so that it would reduce

0:45:45.120 --> 0:45:47.680
<v Speaker 4>our time to bring in the infrastructure online. And at

0:45:47.680 --> 0:45:50.120
<v Speaker 4>that point it was the power supply units and the

0:45:50.200 --> 0:45:53.840
<v Speaker 4>fans for the nodes that the Oliams were putting together,

0:45:54.480 --> 0:45:56.719
<v Speaker 4>and if we hadn't have done that, it would have

0:45:56.719 --> 0:45:59.600
<v Speaker 4>been another i think eight weeks on top of the

0:45:59.640 --> 0:46:03.279
<v Speaker 4>build process, just because not all the components would have

0:46:03.280 --> 0:46:06.359
<v Speaker 4>been there at the same time. So you're navigating this,

0:46:06.960 --> 0:46:10.960
<v Speaker 4>you know, within other kind of global supply chain disruptions

0:46:10.960 --> 0:46:13.160
<v Speaker 4>and inflation and all these other things that are going

0:46:13.160 --> 0:46:16.960
<v Speaker 4>on right now and it's just an insanely complex task

0:46:17.080 --> 0:46:21.640
<v Speaker 4>that I think, you know, the generation of software developers

0:46:21.880 --> 0:46:25.759
<v Speaker 4>and founders that we're working with today were used to

0:46:25.840 --> 0:46:28.480
<v Speaker 4>being able to go to a cloud service provider and

0:46:28.560 --> 0:46:31.560
<v Speaker 4>just getting whatever infrastructure they needed. Right. You go to

0:46:31.600 --> 0:46:33.960
<v Speaker 4>your hyperscalers and say all right, any of this and

0:46:34.000 --> 0:46:37.680
<v Speaker 4>it was just there and available. And that just doesn't

0:46:37.719 --> 0:46:42.560
<v Speaker 4>exist today because the pace of demand growth that we've

0:46:42.600 --> 0:46:45.439
<v Speaker 4>been on and just the lack of this infrastructure's availability,

0:46:45.680 --> 0:46:49.080
<v Speaker 4>and it's just caught everyone by surprise. Again. You're you're

0:46:49.120 --> 0:46:54.120
<v Speaker 4>asking infrastructure to keep pace with the fastest adoption of

0:46:55.080 --> 0:46:57.760
<v Speaker 4>a new piece of software that's ever occurred.

0:46:58.480 --> 0:47:01.440
<v Speaker 1>Brandon McBee, core Leave, Thank you so much. That was

0:47:01.440 --> 0:47:03.960
<v Speaker 1>a great conversation. Like I said, I always sort of

0:47:04.040 --> 0:47:06.520
<v Speaker 1>measure the quality of a conversation of like do I

0:47:06.520 --> 0:47:07.200
<v Speaker 1>get seven.

0:47:07.160 --> 0:47:09.279
<v Speaker 2>How many additional episode like that is.

0:47:09.200 --> 0:47:11.520
<v Speaker 1>A pretty good proxy for a good conversation. Do you

0:47:11.520 --> 0:47:13.480
<v Speaker 1>get like eight ideas for future episodes? We got a

0:47:13.480 --> 0:47:15.920
<v Speaker 1>bunch there, So thank you so much for coming.

0:47:15.719 --> 0:47:16.360
<v Speaker 3>On the podcast.

0:47:16.640 --> 0:47:18.319
<v Speaker 4>Always happy to chat with you guys, and thank you

0:47:18.360 --> 0:47:19.080
<v Speaker 4>for the invitation.

0:47:32.880 --> 0:47:33.280
<v Speaker 3>Tracy.

0:47:33.320 --> 0:47:35.920
<v Speaker 1>I want to find that company that makes the coolant

0:47:36.280 --> 0:47:39.200
<v Speaker 1>for the data No, seriously, for the data centers. That

0:47:39.320 --> 0:47:43.040
<v Speaker 1>allows them to pack more compute and more energy into

0:47:43.080 --> 0:47:45.200
<v Speaker 1>this space, because it's like it feels like they're probably

0:47:45.200 --> 0:47:46.239
<v Speaker 1>going to make a fortune of the.

0:47:46.160 --> 0:47:47.759
<v Speaker 2>Next Joe, I think you just want to talk to

0:47:47.800 --> 0:47:51.640
<v Speaker 2>an HVACT contractor that's like installing out.

0:47:51.880 --> 0:47:52.520
<v Speaker 3>Can we talk to it?

0:47:52.920 --> 0:47:56.000
<v Speaker 1>Just some random like I love the Maybe it was

0:47:56.040 --> 0:47:59.200
<v Speaker 1>such a funny thought like these like really advanced data centers,

0:47:59.280 --> 0:48:00.960
<v Speaker 1>like oh, do we have like a local air conditioning

0:48:00.960 --> 0:48:01.759
<v Speaker 1>guy who can like.

0:48:01.880 --> 0:48:03.520
<v Speaker 2>But I imagine actually that would have been a good

0:48:03.600 --> 0:48:07.120
<v Speaker 2>question for Brandon, wouldn't it. Like the labor constraints in

0:48:07.600 --> 0:48:10.799
<v Speaker 2>building and adapting those data centers. But there was so

0:48:10.920 --> 0:48:12.960
<v Speaker 2>much in there. One of the things, one of the

0:48:12.960 --> 0:48:15.680
<v Speaker 2>things that I was thinking about was the point about how, well, okay,

0:48:15.960 --> 0:48:18.799
<v Speaker 2>if you train a model on one type of chip,

0:48:18.840 --> 0:48:21.600
<v Speaker 2>you're going to keep using that type of chip. And

0:48:21.640 --> 0:48:24.000
<v Speaker 2>I guess, I guess it's kind of obvious, but it

0:48:24.080 --> 0:48:28.560
<v Speaker 2>does suggest that there's some stickiness there, Like if you

0:48:28.640 --> 0:48:32.239
<v Speaker 2>start out using an Nvidia each one hundred, you're going

0:48:32.280 --> 0:48:33.880
<v Speaker 2>to keep using them, and in fact, you're going to

0:48:33.920 --> 0:48:37.800
<v Speaker 2>consume even more because the processing power required the compute

0:48:37.840 --> 0:48:40.880
<v Speaker 2>required for the inference is higher than for the actual

0:48:40.920 --> 0:48:42.080
<v Speaker 2>initial training.

0:48:42.320 --> 0:48:44.760
<v Speaker 1>Which I knew that that was the case because Stacy

0:48:44.800 --> 0:48:47.200
<v Speaker 1>said so as well, but I did not realize quite

0:48:47.200 --> 0:48:51.600
<v Speaker 1>the scale of like how much more Like okay, like

0:48:51.680 --> 0:48:53.400
<v Speaker 1>if you train a model and then we try to

0:48:53.440 --> 0:48:54.840
<v Speaker 1>take it to market product tize it.

0:48:55.000 --> 0:48:56.080
<v Speaker 3>As a business person.

0:48:55.920 --> 0:48:58.319
<v Speaker 1>I'd say, if we try to productize, like how much

0:48:58.480 --> 0:49:02.680
<v Speaker 1>more computing power or we would need for the inferant aspect?

0:49:02.880 --> 0:49:04.520
<v Speaker 1>And meanwhile we have to keep training it all the

0:49:04.560 --> 0:49:05.960
<v Speaker 1>time to keep it up with fresh data and.

0:49:05.920 --> 0:49:06.480
<v Speaker 3>Stuff like that.

0:49:06.600 --> 0:49:10.320
<v Speaker 2>Yeah, totally. And the other thing that I was thinking about,

0:49:10.400 --> 0:49:13.839
<v Speaker 2>and again Stacy mentioned this in our discussion with him

0:49:13.840 --> 0:49:17.480
<v Speaker 2>as well, but this idea of Nvidia building a kind

0:49:17.520 --> 0:49:21.279
<v Speaker 2>of large ecosystem around the hardware. So you have the

0:49:21.360 --> 0:49:24.799
<v Speaker 2>open source software Kudo, which we talked about a little bit,

0:49:25.120 --> 0:49:28.640
<v Speaker 2>and then you have these sort of high touch partnerships

0:49:28.719 --> 0:49:32.520
<v Speaker 2>with companies like core Weave where they're trying to make

0:49:32.560 --> 0:49:35.160
<v Speaker 2>it as easy as possible for you to use their

0:49:35.239 --> 0:49:38.440
<v Speaker 2>chips and set them up in a way that works

0:49:38.480 --> 0:49:42.880
<v Speaker 2>for you. It feels like maybe it feels almost like

0:49:42.920 --> 0:49:44.120
<v Speaker 2>what bitmin used to do.

0:49:44.120 --> 0:49:46.960
<v Speaker 3>Do you remember that, uh, no.

0:49:46.920 --> 0:49:49.680
<v Speaker 2>Maybe they're still doing it anyway, but it does feel

0:49:49.719 --> 0:49:52.920
<v Speaker 2>like they're trying to build this like ecosystem mote around

0:49:53.080 --> 0:49:54.160
<v Speaker 2>the chip technology.

0:49:54.440 --> 0:49:54.680
<v Speaker 4>Yeah.

0:49:54.760 --> 0:49:56.319
<v Speaker 3>No, absolutely true.

0:49:56.360 --> 0:49:58.320
<v Speaker 1>And you know, I really do take that point that

0:49:58.440 --> 0:50:02.040
<v Speaker 1>Brandon made about like every company has a sort of

0:50:02.080 --> 0:50:04.759
<v Speaker 1>like knowledge that cannot be written down on a piece

0:50:04.800 --> 0:50:06.640
<v Speaker 1>of paper. Yeah, which is a Dan Wong point that

0:50:06.680 --> 0:50:08.759
<v Speaker 1>we've been talking about for years. And so it's like

0:50:09.120 --> 0:50:10.840
<v Speaker 1>to your point, you know, like you have to like

0:50:11.080 --> 0:50:13.720
<v Speaker 1>use different types of connectors and different types of power

0:50:13.760 --> 0:50:16.040
<v Speaker 1>and all these stuff like the ease with which any

0:50:16.040 --> 0:50:21.680
<v Speaker 1>sort of traditional cloud provider or data center provider can

0:50:21.920 --> 0:50:23.880
<v Speaker 1>you know, sort of switch to it's like a you know,

0:50:24.000 --> 0:50:25.840
<v Speaker 1>it's not trivial even with lots of no.

0:50:26.400 --> 0:50:29.760
<v Speaker 2>But coming away, I'm coming away from that conversation thinking,

0:50:29.840 --> 0:50:32.799
<v Speaker 2>like the big question here is how quickly can those

0:50:32.840 --> 0:50:37.120
<v Speaker 2>other hyperscalers adapt and like how big a moat can

0:50:37.239 --> 0:50:38.960
<v Speaker 2>Nvidia build around this business?

0:50:39.000 --> 0:50:41.160
<v Speaker 1>And then I mean the other question I have is

0:50:41.280 --> 0:50:44.040
<v Speaker 1>like what if none of these companies make any money

0:50:44.400 --> 0:50:46.600
<v Speaker 1>building AI models, Like I still don't think like that's

0:50:46.640 --> 0:50:48.800
<v Speaker 1>been proven and so you can have this like huge

0:50:48.840 --> 0:50:50.520
<v Speaker 1>boom and like, hey, we got to build any by

0:50:50.640 --> 0:50:52.920
<v Speaker 1>a model is what we're going to build, like you know,

0:50:53.120 --> 0:50:56.440
<v Speaker 1>outlaws GPT for like data stuff and whatever. But it

0:50:56.640 --> 0:50:59.759
<v Speaker 1>all is somewhat predicated on these companies being successful and

0:50:59.760 --> 0:51:02.040
<v Speaker 1>making a lot of money. And if they're not, and

0:51:02.040 --> 0:51:04.720
<v Speaker 1>if it turns out that like the monetization of AI

0:51:04.840 --> 0:51:08.320
<v Speaker 1>products is trickier than expected, then that also raises this

0:51:08.440 --> 0:51:09.640
<v Speaker 1>question about like how long.

0:51:09.480 --> 0:51:12.480
<v Speaker 2>This Like I'm sorry, Joe, so you're saying that tech

0:51:12.520 --> 0:51:16.319
<v Speaker 2>companies should make money? Is that it? Are you sure?

0:51:17.120 --> 0:51:20.640
<v Speaker 3>That's right? That's it's real post zerp thinking of it?

0:51:20.960 --> 0:51:23.000
<v Speaker 2>I know, all right? Shall we leave it there?

0:51:23.040 --> 0:51:23.719
<v Speaker 3>Let's leave it there.

0:51:23.800 --> 0:51:26.640
<v Speaker 2>This has been another episode of the All Thoughts podcast.

0:51:26.680 --> 0:51:29.279
<v Speaker 2>I'm Tracy Alloway. You can follow me on Twitter at

0:51:29.320 --> 0:51:30.520
<v Speaker 2>Tracy Alloway.

0:51:30.160 --> 0:51:32.480
<v Speaker 1>And I'm Joe Wisenthal. You can follow me on Twitter

0:51:32.560 --> 0:51:35.160
<v Speaker 1>at the Stalwart. Follow our guest Brannon McBee.

0:51:35.200 --> 0:51:36.680
<v Speaker 3>He's at Brannon McBee.

0:51:36.840 --> 0:51:40.279
<v Speaker 1>Follow our producers Carmen Rodriguez at Carmen Arman and dash

0:51:40.280 --> 0:51:42.600
<v Speaker 1>Ol Bennett at dashbot. And check out all of the

0:51:42.600 --> 0:51:46.200
<v Speaker 1>Bloomberg podcasts under the handle at podcasts, and for more

0:51:46.239 --> 0:51:49.359
<v Speaker 1>Odd Lots content, go to Bloomberg dot com slash odd

0:51:49.360 --> 0:51:52.560
<v Speaker 1>lots where we have transcripts, a blog, and a newsletter

0:51:52.600 --> 0:51:55.760
<v Speaker 1>that comes out each Friday. And check out our Discord.

0:51:55.920 --> 0:51:58.920
<v Speaker 1>We have an AI channel and a semiconductor channel in

0:51:58.960 --> 0:52:01.280
<v Speaker 1>there so people talk about these topics twenty four to seven.

0:52:01.480 --> 0:52:02.120
<v Speaker 3>Maybe they'll be.

0:52:02.040 --> 0:52:04.799
<v Speaker 1>Talking about them in both of those rooms when this

0:52:04.880 --> 0:52:08.080
<v Speaker 1>comes out. Discord dot gg, slash.

0:52:07.719 --> 0:52:11.520
<v Speaker 2>Outline and if you enjoy all thoughts, if you appreciate

0:52:11.520 --> 0:52:14.080
<v Speaker 2>conversations like the one we just had with Brandon McBee,

0:52:14.160 --> 0:52:17.960
<v Speaker 2>then please leave us a positive review on your favorite

0:52:18.080 --> 0:52:20.080
<v Speaker 2>podcast platform. Thanks for listening.