WEBVTT - Data Center Dynamics: AI and Energy Demand

0:00:00.280 --> 0:00:03.040
<v Speaker 1>This is Dana Perkins and you're listening to Switched on

0:00:03.279 --> 0:00:06.960
<v Speaker 1>the BNAF podcast. Today we bring you a recording from

0:00:06.960 --> 0:00:10.040
<v Speaker 1>our BNAF summit in San Francisco, which took place on

0:00:10.080 --> 0:00:13.440
<v Speaker 1>the fourth and fifth of February. The panel was titled

0:00:13.680 --> 0:00:17.800
<v Speaker 1>Data Dynamics. Now certainly a hot topic in energy circles

0:00:17.880 --> 0:00:20.560
<v Speaker 1>has been the growth in data centers and how AI

0:00:20.880 --> 0:00:23.680
<v Speaker 1>has led to a rise in demand for power. In

0:00:23.800 --> 0:00:26.360
<v Speaker 1>order to meet this, big tech companies are looking for

0:00:26.440 --> 0:00:30.240
<v Speaker 1>solutions and firms like Google are signing power purchase agreements

0:00:30.320 --> 0:00:33.920
<v Speaker 1>in an array of technologies like nuclear, long duration energy storage,

0:00:33.960 --> 0:00:38.520
<v Speaker 1>and even geothermal. While these data centers are undeniably energy intensive,

0:00:38.600 --> 0:00:42.479
<v Speaker 1>efficiencies can be found when it comes to reducing load requirements.

0:00:42.760 --> 0:00:45.480
<v Speaker 1>This is seen with the recent release of Deepseek's AI

0:00:45.560 --> 0:00:48.680
<v Speaker 1>model in January twenty twenty five. On today's show, the

0:00:48.720 --> 0:00:52.839
<v Speaker 1>panelists discuss the increasing capital expenditure on data centers, as

0:00:52.880 --> 0:00:55.400
<v Speaker 1>well as what has been driving the decision making of

0:00:55.440 --> 0:00:58.120
<v Speaker 1>big tech companies when it comes to this spend and

0:00:58.240 --> 0:01:01.720
<v Speaker 1>how potential bottlenecks might slow them down. The panelists include

0:01:01.760 --> 0:01:06.080
<v Speaker 1>Stephen Carlini, Chief Advocate Data Centers and AI at Schneider Electric,

0:01:06.400 --> 0:01:09.600
<v Speaker 1>Will Conkling, head of Data Center Energy for the America's

0:01:09.600 --> 0:01:13.280
<v Speaker 1>in Amia at Google, Kleiber Costa, chief commercial officer for

0:01:13.480 --> 0:01:17.160
<v Speaker 1>AS Corporation, and Darwesh Singh, the founder and CEO of

0:01:17.200 --> 0:01:21.160
<v Speaker 1>Bold Graphics. The panel was moderated by Mark Daily, BNF's

0:01:21.200 --> 0:01:25.319
<v Speaker 1>head of Technology and Innovation. For more information about BNF

0:01:25.400 --> 0:01:27.920
<v Speaker 1>Summit's taking place around the world, as well as our

0:01:28.000 --> 0:01:30.120
<v Speaker 1>upcoming event in New York on the twenty ninth and

0:01:30.160 --> 0:01:32.760
<v Speaker 1>thirtieth of April, an to view recordings from this and

0:01:32.840 --> 0:01:36.399
<v Speaker 1>other previous events, head to about dot BNF dot com

0:01:36.400 --> 0:01:39.320
<v Speaker 1>Forward Slash Summit. Right now, let's hear from our panel

0:01:39.440 --> 0:01:48.440
<v Speaker 1>regarding power demand and data centers.

0:01:52.800 --> 0:01:55.160
<v Speaker 2>Thank you everyone very much for joining us here today.

0:01:56.880 --> 0:02:00.480
<v Speaker 2>We've heard an awful lot about the energy transition, like

0:02:00.600 --> 0:02:02.880
<v Speaker 2>at all be enough events, and I imagine a lot

0:02:02.880 --> 0:02:05.240
<v Speaker 2>of events that everyone here goes to. It's very energy

0:02:05.240 --> 0:02:08.600
<v Speaker 2>focused group, transport focused group, but there's lots of big

0:02:08.600 --> 0:02:11.720
<v Speaker 2>transitions happening in the global economy. We're here today to

0:02:11.760 --> 0:02:14.799
<v Speaker 2>talk about the intersection of the energy transition with one

0:02:14.840 --> 0:02:18.480
<v Speaker 2>of the other really big transformations in the economy, maybe

0:02:18.480 --> 0:02:21.000
<v Speaker 2>the biggest one of our lifetime. If you believe some people.

0:02:21.680 --> 0:02:24.560
<v Speaker 2>So we're here to talk about data centers, energy demand,

0:02:24.720 --> 0:02:29.360
<v Speaker 2>artificial intelligence. I'm joined here today by Stephen Carlini, Chief

0:02:29.400 --> 0:02:33.080
<v Speaker 2>Advocate Data Centers and AI at Schneider Electric, Will Conkling,

0:02:33.240 --> 0:02:37.400
<v Speaker 2>head of Data Center Energy America's Animea at Google, Clever Costa,

0:02:38.639 --> 0:02:42.080
<v Speaker 2>chief commercial Officer at the AEES Corporation, and Darbush Sing,

0:02:42.080 --> 0:02:46.960
<v Speaker 2>Founder and CEO of Bolt Graphics. So the first thing

0:02:47.000 --> 0:02:49.560
<v Speaker 2>that I want to talk about is really why has

0:02:49.560 --> 0:02:54.240
<v Speaker 2>there been so much interest in data centers this year? Like,

0:02:54.320 --> 0:02:56.240
<v Speaker 2>let's just start from the beginning. What's causing out go

0:02:56.240 --> 0:02:58.320
<v Speaker 2>to you first, Star Resh, and if everyone can actually

0:02:58.360 --> 0:03:01.120
<v Speaker 2>just introduce themselves and kind of their view on the

0:03:01.160 --> 0:03:03.280
<v Speaker 2>industry in their first answer, that'd be great.

0:03:03.560 --> 0:03:04.440
<v Speaker 3>Yeah. Thanks Mark.

0:03:05.240 --> 0:03:08.240
<v Speaker 4>I'm dar Wesh Funer Ceobo Graphics. We are a semi

0:03:08.240 --> 0:03:11.800
<v Speaker 4>conductory startup focusing on GPUs. My background is in building

0:03:11.840 --> 0:03:14.800
<v Speaker 4>data centers, so I share a lot of the pains

0:03:15.400 --> 0:03:18.560
<v Speaker 4>at the panel and in the industry in general. Mark,

0:03:18.600 --> 0:03:23.760
<v Speaker 4>I think to your question, compute requirements have always been increasing.

0:03:23.800 --> 0:03:25.760
<v Speaker 4>This is I think it's not new to anyone. We

0:03:25.800 --> 0:03:29.799
<v Speaker 4>have phones now that are more powerful than PlayStation fours

0:03:29.880 --> 0:03:33.160
<v Speaker 4>from twelve years ago. What is new, though, is the

0:03:33.280 --> 0:03:38.400
<v Speaker 4>demand for ten years in the future computing power right now.

0:03:38.680 --> 0:03:41.680
<v Speaker 4>And a lot of these AI companies, whether they're training models,

0:03:42.080 --> 0:03:45.880
<v Speaker 4>whether they're building data centers to host these models, or

0:03:45.880 --> 0:03:48.520
<v Speaker 4>whether they're making phones that can run inference on these things,

0:03:48.520 --> 0:03:51.160
<v Speaker 4>they want it right now. And so I think that

0:03:51.200 --> 0:03:53.040
<v Speaker 4>creates a lot of interest, a lot of hype. It

0:03:53.080 --> 0:03:57.680
<v Speaker 4>also creates an opportunity for new players in the market

0:03:57.680 --> 0:03:59.720
<v Speaker 4>to come in, whether they're DC builders that can build

0:03:59.760 --> 0:04:03.480
<v Speaker 4>data centers in six months instead of four years, small

0:04:04.160 --> 0:04:07.240
<v Speaker 4>modular nuclear reactor companies that are building these and seven

0:04:07.320 --> 0:04:09.760
<v Speaker 4>years instead of twenty five years. So I think it's

0:04:09.800 --> 0:04:11.640
<v Speaker 4>just like a timeline. Let's shift all this left. I

0:04:11.720 --> 0:04:13.720
<v Speaker 4>want to do right now and what does that really enable?

0:04:14.680 --> 0:04:17.840
<v Speaker 2>Okay, and so Stephen, could you give us a primer

0:04:17.880 --> 0:04:21.120
<v Speaker 2>on how Schneider Electric relates to this conversation and when

0:04:21.200 --> 0:04:24.920
<v Speaker 2>did your job change in this kind of this new

0:04:25.360 --> 0:04:26.680
<v Speaker 2>hype cycle that we're going through.

0:04:27.520 --> 0:04:30.640
<v Speaker 5>Yeah, Kinder Electric, if you're not familiar with this largest

0:04:31.040 --> 0:04:34.960
<v Speaker 5>power and cooling solution provider for data centers in the world,

0:04:35.279 --> 0:04:37.960
<v Speaker 5>and as you said in an earlier panel, you know

0:04:38.000 --> 0:04:40.719
<v Speaker 5>AI is not new AI has been around for a while.

0:04:40.760 --> 0:04:43.440
<v Speaker 5>We've been talking to a lot of the hyperscalers. We

0:04:43.520 --> 0:04:47.400
<v Speaker 5>have staff of people signed to each hyperscaler, each large COLO,

0:04:47.520 --> 0:04:52.760
<v Speaker 5>each large enterprise accounts. And we you know, we noticed

0:04:53.080 --> 0:04:55.800
<v Speaker 5>five or six years ago, you know, these data centers

0:04:55.800 --> 0:04:57.880
<v Speaker 5>can't be built overnight. And five or six years ago,

0:04:57.920 --> 0:04:59.680
<v Speaker 5>a lot of the hyper scalers were coming to us,

0:04:59.800 --> 0:05:02.200
<v Speaker 5>not only talking to us about higher densities, but higher

0:05:02.279 --> 0:05:05.120
<v Speaker 5>densities and scales that we've never heard of. You know,

0:05:05.200 --> 0:05:07.800
<v Speaker 5>twenty twenty megawat data centers. Back then it was a

0:05:07.800 --> 0:05:10.600
<v Speaker 5>big data center. They're talking one hundred, one hundred and

0:05:10.640 --> 0:05:13.880
<v Speaker 5>fifty three hundred megawat campuses back then, and we're like, wow,

0:05:13.920 --> 0:05:17.240
<v Speaker 5>this is this is a big change. So the densities,

0:05:17.720 --> 0:05:22.039
<v Speaker 5>you know, started to really change when Nvidia came out

0:05:22.080 --> 0:05:24.680
<v Speaker 5>with you know, the A one hundreds and the.

0:05:24.600 --> 0:05:25.400
<v Speaker 3>A one hundreds.

0:05:26.360 --> 0:05:29.720
<v Speaker 5>It was about three years ago and and the A

0:05:29.839 --> 0:05:32.760
<v Speaker 5>one hundreds were kind of the first you know, at

0:05:32.760 --> 0:05:35.680
<v Speaker 5>scale deployments for a lot of the hyperscalers, and a

0:05:35.720 --> 0:05:37.280
<v Speaker 5>lot of those were air cool they were twenty five

0:05:37.360 --> 0:05:40.680
<v Speaker 5>kilowats parac Then you saw the grace hoppers, which were

0:05:41.800 --> 0:05:45.040
<v Speaker 5>last year, which were thirty six kilowats are acting seventy

0:05:45.040 --> 0:05:48.080
<v Speaker 5>two kilowats parak and now we have the Blackwells. The

0:05:48.120 --> 0:05:50.640
<v Speaker 5>black Wells are one hundred and thirty two kilowats per rack,

0:05:51.160 --> 0:05:54.240
<v Speaker 5>which is really pushing the limit of what we can

0:05:54.279 --> 0:05:58.000
<v Speaker 5>get powered to these racks and cooling to these racks. Next,

0:05:58.240 --> 0:06:02.000
<v Speaker 5>they're working on Ruben, which is the next generation. They're

0:06:02.000 --> 0:06:04.680
<v Speaker 5>already we're already working on the designs for that at

0:06:04.680 --> 0:06:08.240
<v Speaker 5>two hundred and forty kilowats per rack. So it's just exponentially.

0:06:08.320 --> 0:06:11.440
<v Speaker 5>For years, it was just two socket x eighty six

0:06:11.680 --> 0:06:14.760
<v Speaker 5>pizza box servers in these data centers, and we were

0:06:14.760 --> 0:06:17.320
<v Speaker 5>doing ten kilo wats per rack. And in the last

0:06:17.400 --> 0:06:20.599
<v Speaker 5>four or five years, it's just exponentially, you know, increased,

0:06:20.920 --> 0:06:23.240
<v Speaker 5>and not just increased in small scale, but it's a

0:06:23.320 --> 0:06:24.599
<v Speaker 5>large scale that we talked about.

0:06:25.040 --> 0:06:28.359
<v Speaker 2>Okay, so will you're you're coming from Google, the company

0:06:28.360 --> 0:06:30.320
<v Speaker 2>that started the all it was Google's R and D

0:06:30.400 --> 0:06:34.080
<v Speaker 2>Live a transformer and Google's obviously been a huge energy

0:06:34.080 --> 0:06:38.520
<v Speaker 2>procurement company for years and years though and when did

0:06:38.560 --> 0:06:40.840
<v Speaker 2>when did this translate into changes in your job? The

0:06:41.000 --> 0:06:42.880
<v Speaker 2>recent technology advances.

0:06:43.680 --> 0:06:47.080
<v Speaker 6>Yeah, so the story for me is like I've been

0:06:47.080 --> 0:06:49.480
<v Speaker 6>at Google just over ten years in some way to

0:06:49.560 --> 0:06:53.400
<v Speaker 6>performed buying energy for data centers and buying renewal energy

0:06:53.400 --> 0:06:56.080
<v Speaker 6>for data centers, and working with utilities and working energy supply.

0:06:56.600 --> 0:06:59.320
<v Speaker 6>And you know, Google has been an AI first company

0:06:59.440 --> 0:07:01.680
<v Speaker 6>since about like twenty sixteen, twenty seventeen. Our CEO has

0:07:01.720 --> 0:07:03.360
<v Speaker 6>been saying that for a long time, right, And we've

0:07:03.400 --> 0:07:06.400
<v Speaker 6>been infusing AI and machine learning into our products since

0:07:06.400 --> 0:07:09.679
<v Speaker 6>then in various various ways that you know, we probably

0:07:09.720 --> 0:07:12.240
<v Speaker 6>don't notice as users, but it's been there. And then

0:07:12.560 --> 0:07:14.320
<v Speaker 6>in the last you know, eighteen months or so, it

0:07:14.360 --> 0:07:16.160
<v Speaker 6>see the emergence of you know, sort of more consumer

0:07:16.240 --> 0:07:20.400
<v Speaker 6>facing pure mL and AI products you know before so,

0:07:20.480 --> 0:07:23.520
<v Speaker 6>like i'd say, mid twenty twenty three was kind of

0:07:23.840 --> 0:07:27.920
<v Speaker 6>a watershed moment for us, but we saw the green

0:07:28.000 --> 0:07:30.640
<v Speaker 6>suits of this before that, when you know, the grid

0:07:30.720 --> 0:07:36.760
<v Speaker 6>started to see demand growth, you know, generally across a

0:07:36.840 --> 0:07:39.400
<v Speaker 6>number of sectors and industries, right from more manufacturing and

0:07:39.440 --> 0:07:43.360
<v Speaker 6>more batteries and manufacturing and more car manufacturing and more

0:07:43.400 --> 0:07:45.280
<v Speaker 6>s reshoring of a lot of stuff back to the US,

0:07:46.120 --> 0:07:49.080
<v Speaker 6>and that started to manifest itself, right, and utilities coming

0:07:49.120 --> 0:07:50.840
<v Speaker 6>to us and saying, you know, they have to buil

0:07:50.840 --> 0:07:53.400
<v Speaker 6>out their transmission system in ways that they hadn't anticipated

0:07:53.440 --> 0:07:55.920
<v Speaker 6>in order to continue to serve load. And that's sort

0:07:55.920 --> 0:07:57.600
<v Speaker 6>of you know, power for the course as business as

0:07:57.680 --> 0:08:02.320
<v Speaker 6>usual for us. You couple that sort of like growth

0:08:02.400 --> 0:08:05.120
<v Speaker 6>of going from twenty years ago or sorry for the

0:08:05.200 --> 0:08:07.920
<v Speaker 6>last twenty years twenty twenty three of zero point five

0:08:07.960 --> 0:08:11.200
<v Speaker 6>percent annual growth on the grid to to three four

0:08:11.360 --> 0:08:13.200
<v Speaker 6>now four and a half five percent annual growth from

0:08:13.200 --> 0:08:15.960
<v Speaker 6>the grid, and then you have an emergence of a

0:08:16.000 --> 0:08:18.320
<v Speaker 6>new sort of large you know, data center demand with

0:08:18.400 --> 0:08:20.800
<v Speaker 6>machine learning chips to what Steve has talked about with

0:08:20.800 --> 0:08:23.920
<v Speaker 6>with nvidious chips and then our own internal tens of

0:08:23.960 --> 0:08:27.760
<v Speaker 6>processing units. We saw in mid twenty twenty three the

0:08:27.880 --> 0:08:32.280
<v Speaker 6>sort of crossover point from you know, being able to

0:08:32.360 --> 0:08:34.640
<v Speaker 6>sort of generally source power where when we needed it

0:08:34.760 --> 0:08:37.040
<v Speaker 6>on a timescal that made sense to us, to an

0:08:37.080 --> 0:08:40.880
<v Speaker 6>acceleration of demand to what Darbush just said around you know,

0:08:41.080 --> 0:08:43.680
<v Speaker 6>needing it sooner, and then a push out of lead

0:08:43.679 --> 0:08:45.439
<v Speaker 6>times on some of the grid buildout and some of

0:08:45.720 --> 0:08:48.679
<v Speaker 6>and serving that demand by utilities, and it's a it

0:08:48.800 --> 0:08:52.439
<v Speaker 6>was kind of a collision of technology sort of product

0:08:52.920 --> 0:08:59.040
<v Speaker 6>development curves and infrastructure timelines that don't always mesh well.

0:08:59.240 --> 0:09:01.200
<v Speaker 6>And we've been kind of been in that that soup

0:09:01.280 --> 0:09:03.200
<v Speaker 6>ever since. And it's I like to say, it's been

0:09:03.240 --> 0:09:04.800
<v Speaker 6>one of the more dynamic times in my career. And

0:09:04.800 --> 0:09:06.959
<v Speaker 6>I don't thpect I'll see anything like I would again, So.

0:09:08.080 --> 0:09:10.880
<v Speaker 2>And clever, let's get the energy company perspective on this.

0:09:11.559 --> 0:09:13.680
<v Speaker 2>When did you start noticing a big change from what

0:09:13.800 --> 0:09:14.280
<v Speaker 2>was happening.

0:09:14.640 --> 0:09:18.080
<v Speaker 7>Look, I think if you hear my my my colleagues

0:09:18.120 --> 0:09:21.280
<v Speaker 7>here on the panel, it has been about a lot

0:09:21.280 --> 0:09:24.280
<v Speaker 7>of changes over a very short period of time, a

0:09:24.320 --> 0:09:27.440
<v Speaker 7>lot of volatility. I would say, you know, I think,

0:09:28.000 --> 0:09:32.440
<v Speaker 7>I think you'll see, uh, these these massive growth over

0:09:32.440 --> 0:09:37.880
<v Speaker 7>the past few years projections and then one day opened

0:09:38.040 --> 0:09:41.600
<v Speaker 7>the papers and there's deep, deep seek there changing everything

0:09:41.640 --> 0:09:43.280
<v Speaker 7>and you don't know what is true what is not.

0:09:43.520 --> 0:09:47.240
<v Speaker 7>So everybody's trying to figure figure that out. Look the industry,

0:09:47.320 --> 0:09:51.480
<v Speaker 7>I'm with AES corporation. I've been at AS for for

0:09:51.520 --> 0:09:53.679
<v Speaker 7>about seven years there, but I've been in the energy

0:09:53.800 --> 0:09:56.880
<v Speaker 7>business for about twenty five years. I started my career

0:09:56.960 --> 0:10:00.439
<v Speaker 7>right when air Ron was the greatest thing on earth.

0:10:00.960 --> 0:10:04.280
<v Speaker 7>Everybody wanted to work for and run not not after

0:10:04.320 --> 0:10:08.640
<v Speaker 7>that and Ron, we all know what happened. And then UH,

0:10:08.679 --> 0:10:11.400
<v Speaker 7>there's the boom and bust on the gas cycle. Hainesville

0:10:11.440 --> 0:10:17.760
<v Speaker 7>Economics showed up with Shell Gas UH. A lot of

0:10:17.800 --> 0:10:21.680
<v Speaker 7>companies also went bankrupt, and volatility in the in the

0:10:21.800 --> 0:10:24.640
<v Speaker 7>energy sector disappeared for a long period of time, with

0:10:24.880 --> 0:10:29.840
<v Speaker 7>very small growth over the past five years or maybe

0:10:29.840 --> 0:10:33.720
<v Speaker 7>a little a little more, as Will said, is explosive demand.

0:10:33.880 --> 0:10:37.520
<v Speaker 7>I think it's been one of the most dynamics periods

0:10:37.559 --> 0:10:39.360
<v Speaker 7>of times of my career as well.

0:10:39.920 --> 0:10:41.040
<v Speaker 3>But I guess the point here.

0:10:40.960 --> 0:10:45.280
<v Speaker 7>Is that the energy the industry is not UH is

0:10:45.440 --> 0:10:49.400
<v Speaker 7>very familiar with challenges and how to overcome those challenges.

0:10:49.720 --> 0:10:53.640
<v Speaker 7>So I think my job really changed when when we

0:10:53.720 --> 0:10:59.559
<v Speaker 7>moved from being providers of projects of or or or

0:10:59.679 --> 0:11:04.840
<v Speaker 7>or or technology to partnering with some of these hyperscalers,

0:11:05.120 --> 0:11:11.440
<v Speaker 7>some of these large data center companies and start putting

0:11:11.440 --> 0:11:15.200
<v Speaker 7>together solutions with them. Not only at AS, not only

0:11:15.240 --> 0:11:20.120
<v Speaker 7>we're one of the largest according to bn EF. Actually

0:11:20.120 --> 0:11:25.440
<v Speaker 7>we're the largest provider of renewable energy to corporates over

0:11:25.480 --> 0:11:28.480
<v Speaker 7>the past three years, so we know how that works.

0:11:28.520 --> 0:11:31.800
<v Speaker 7>But we also own utility companies. We own utilities in

0:11:31.800 --> 0:11:36.400
<v Speaker 7>Ohio and Indiana, and we work very closely with those

0:11:36.800 --> 0:11:39.720
<v Speaker 7>hyper scalers and data center companies to meet their needs

0:11:39.760 --> 0:11:41.120
<v Speaker 7>at the utility level as well.

0:11:41.480 --> 0:11:43.440
<v Speaker 3>But again, I think the biggest takeaway.

0:11:44.559 --> 0:11:49.880
<v Speaker 7>It feels very very uncertain in terms of demand projections.

0:11:49.880 --> 0:11:53.559
<v Speaker 7>We're going to talk about that later. But whatever projections

0:11:53.600 --> 0:11:58.280
<v Speaker 7>you look, however you slice and dice there. The growth

0:11:58.360 --> 0:12:02.719
<v Speaker 7>is here, is real, and I think the industry is

0:12:04.320 --> 0:12:08.719
<v Speaker 7>everybody said to meet those challenges and meet solutions for

0:12:09.600 --> 0:12:10.120
<v Speaker 7>that growth.

0:12:10.440 --> 0:12:13.000
<v Speaker 2>So this growth is real, we need to deal with it.

0:12:13.520 --> 0:12:16.320
<v Speaker 2>What's been a big question that I've been asked actually

0:12:16.360 --> 0:12:20.320
<v Speaker 2>a lot in my role is does this look different

0:12:20.400 --> 0:12:23.120
<v Speaker 2>than the data center growth that came before? With the

0:12:23.160 --> 0:12:27.000
<v Speaker 2>idea being data centers have been cited close to populations

0:12:27.120 --> 0:12:29.440
<v Speaker 2>so that latency is low and your Netflix loads really quick.

0:12:30.160 --> 0:12:31.960
<v Speaker 2>But that might not be the case for a new

0:12:32.000 --> 0:12:35.360
<v Speaker 2>AI applications where actually training doesn't need to take place

0:12:35.520 --> 0:12:37.600
<v Speaker 2>close to people. Maybe it'll take place in a far

0:12:37.640 --> 0:12:42.840
<v Speaker 2>away place. Starsh what's your sense of this kind of

0:12:42.920 --> 0:12:44.120
<v Speaker 2>regional dynamic.

0:12:45.240 --> 0:12:50.720
<v Speaker 4>Yeah, definitely, AI is changing the requirements for where you

0:12:50.720 --> 0:12:53.360
<v Speaker 4>build data centers, where you can source power and also

0:12:53.400 --> 0:12:56.160
<v Speaker 4>the conversation. Like I think four years ago, if I

0:12:56.200 --> 0:12:58.959
<v Speaker 4>had a conversation with someone about sourcing like hydrogen power

0:12:58.960 --> 0:13:00.640
<v Speaker 4>for a data center, be laughed at.

0:13:01.080 --> 0:13:03.400
<v Speaker 3>And now I'd be laughed at, but like a lot less.

0:13:03.600 --> 0:13:07.200
<v Speaker 4>I think I'd be pointed towards other areas maybe in

0:13:07.240 --> 0:13:07.720
<v Speaker 4>this direction.

0:13:08.720 --> 0:13:10.920
<v Speaker 3>But definitely.

0:13:12.760 --> 0:13:15.240
<v Speaker 4>The workload that that's running in the data center does

0:13:15.360 --> 0:13:18.120
<v Speaker 4>impact really heavily what those requirements are where I can

0:13:18.160 --> 0:13:20.480
<v Speaker 4>put that data center. And now with training and with

0:13:20.920 --> 0:13:25.160
<v Speaker 4>let's say training is a batch workload, all right, HPEC

0:13:25.320 --> 0:13:28.000
<v Speaker 4>supercomputing is also a batch workload that can also be

0:13:28.080 --> 0:13:32.440
<v Speaker 4>an maybe choose Jensen's common It can be an Antarctica somewhere, right,

0:13:32.480 --> 0:13:34.839
<v Speaker 4>it doesn't be very close to me. So yeah, that

0:13:35.240 --> 0:13:38.040
<v Speaker 4>definitely does change, But I don't think it changes the

0:13:38.320 --> 0:13:41.480
<v Speaker 4>economics that much because you still have to deliver a

0:13:41.520 --> 0:13:43.040
<v Speaker 4>lot of power to it. You still need a really

0:13:43.080 --> 0:13:46.840
<v Speaker 4>fat gigabit multi hunter gigabit network link, and these requirements

0:13:46.880 --> 0:13:50.400
<v Speaker 4>like haven't really changed, I think, to be honest, Like,

0:13:50.400 --> 0:13:51.920
<v Speaker 4>if you're going to build a lot of data centers,

0:13:51.960 --> 0:13:54.520
<v Speaker 4>you're already going in the direction of, hey, I need

0:13:54.520 --> 0:13:57.400
<v Speaker 4>to build these further and further away from large metropolitan

0:13:57.440 --> 0:13:58.920
<v Speaker 4>areas because I can't get power anyway.

0:13:59.000 --> 0:14:00.520
<v Speaker 3>So this is a problem like three four years ago,

0:14:00.840 --> 0:14:01.640
<v Speaker 3>it's just worse now.

0:14:02.240 --> 0:14:05.079
<v Speaker 2>Well, actually, interested in you, you're the energy part of

0:14:05.120 --> 0:14:08.719
<v Speaker 2>the equation at Google. Can you give us a bit

0:14:08.760 --> 0:14:12.040
<v Speaker 2>of information? How does that factor into decision making rom

0:14:12.080 --> 0:14:15.120
<v Speaker 2>where to put data centers? Is it it's decided where

0:14:15.160 --> 0:14:16.960
<v Speaker 2>it goes and then we need to find energy or

0:14:17.080 --> 0:14:18.600
<v Speaker 2>is it part of the decision making process?

0:14:18.720 --> 0:14:20.000
<v Speaker 3>Is that the first thing you decide on?

0:14:21.440 --> 0:14:26.840
<v Speaker 6>Yes? And yes it you know historically so before you know,

0:14:26.960 --> 0:14:28.840
<v Speaker 6>before the growth and the grid that I talked about

0:14:29.040 --> 0:14:31.520
<v Speaker 6>kind of started. You know, it's not quite true, but

0:14:31.520 --> 0:14:33.000
<v Speaker 6>you could almost like throw a dart on a map

0:14:33.040 --> 0:14:35.520
<v Speaker 6>and you know, if you were somewhere within a reasonable

0:14:35.560 --> 0:14:38.240
<v Speaker 6>distance of a metropolitan area, you could probably find power

0:14:38.240 --> 0:14:39.840
<v Speaker 6>and a utility would at least build something for you

0:14:39.880 --> 0:14:41.680
<v Speaker 6>in a couple of years, right, And and that was

0:14:41.720 --> 0:14:46.680
<v Speaker 6>generally okay. You know, today, available grid and available generation

0:14:46.880 --> 0:14:49.360
<v Speaker 6>on that grid are are more scarce, at least for

0:14:49.440 --> 0:14:51.520
<v Speaker 6>the you know, short to medium term, right, And so

0:14:51.560 --> 0:14:53.920
<v Speaker 6>you have to be sort of smarter and better at

0:14:53.920 --> 0:14:57.080
<v Speaker 6>picking locations that have available power in the time scale

0:14:57.120 --> 0:15:00.000
<v Speaker 6>you're looking for and and and sort of act quick

0:15:00.080 --> 0:15:04.720
<v Speaker 6>to go and and reserve it and use it, right. So,

0:15:04.720 --> 0:15:08.640
<v Speaker 6>so yet, yes, it's a it's a more important factor

0:15:09.320 --> 0:15:12.320
<v Speaker 6>for us than maybe it was in the past. But

0:15:12.440 --> 0:15:15.200
<v Speaker 6>it doesn't I think divers to your last point there.

0:15:15.200 --> 0:15:17.120
<v Speaker 6>It's like if you go in the middle of nowhere,

0:15:17.360 --> 0:15:19.320
<v Speaker 6>like there isn't power, there isn't fiber, there isn't there

0:15:19.320 --> 0:15:21.880
<v Speaker 6>aren't people to build things, right, There's just these things

0:15:21.880 --> 0:15:26.040
<v Speaker 6>require a certain amount of infrastructure and civilization around them

0:15:26.080 --> 0:15:28.040
<v Speaker 6>to support them, right, and no one wants to live

0:15:28.040 --> 0:15:29.240
<v Speaker 6>next to it. You have to have people that work

0:15:29.240 --> 0:15:31.960
<v Speaker 6>there all the time, right like so so so there's

0:15:32.000 --> 0:15:34.960
<v Speaker 6>there's that factor. And and then our products also like

0:15:35.520 --> 0:15:36.960
<v Speaker 6>don't want to be in the middle of nowhere if

0:15:37.000 --> 0:15:39.320
<v Speaker 6>they can help it. Because if you build a building

0:15:39.480 --> 0:15:42.600
<v Speaker 6>for a data center, and and and so I'll back up.

0:15:42.640 --> 0:15:44.840
<v Speaker 6>There's there's a few different ways that or its fuveent

0:15:44.840 --> 0:15:46.640
<v Speaker 6>things that happen in an mL data center, right or

0:15:46.800 --> 0:15:49.080
<v Speaker 6>a data center. One, you could be training at Google

0:15:49.080 --> 0:15:51.480
<v Speaker 6>at least an internal model too. You could have a

0:15:51.520 --> 0:15:54.040
<v Speaker 6>customer paying you to be able to train their model, right,

0:15:54.360 --> 0:15:56.480
<v Speaker 6>or Three, you could be serving a model or serve

0:15:56.560 --> 0:15:59.720
<v Speaker 6>doing inference and serving AI to customers, right. Only that

0:15:59.800 --> 0:16:02.480
<v Speaker 6>first thing really is that flexible because our customers still

0:16:02.480 --> 0:16:04.480
<v Speaker 6>want to be like within spitting distance of their of

0:16:04.480 --> 0:16:07.080
<v Speaker 6>their footprint on the cloud. And then for inference, we

0:16:07.120 --> 0:16:09.120
<v Speaker 6>still want to be having little latency service to our

0:16:09.160 --> 0:16:12.440
<v Speaker 6>to our consumers, right. And so the internal training, yes,

0:16:12.480 --> 0:16:14.320
<v Speaker 6>it's more flexible. But if you build a data in

0:16:14.360 --> 0:16:15.880
<v Speaker 6>the middle of nowhere just for that and then you

0:16:15.920 --> 0:16:18.120
<v Speaker 6>finish that job, you actually have a Strandard asset, right.

0:16:18.120 --> 0:16:19.720
<v Speaker 6>And so if you think about efficiency of capital and

0:16:19.760 --> 0:16:21.520
<v Speaker 6>how you want to be able to reuse your capital

0:16:21.560 --> 0:16:24.720
<v Speaker 6>and recycle it, you actually don't necessarily always want to

0:16:24.760 --> 0:16:27.520
<v Speaker 6>be just going far afield to to you know, the

0:16:28.080 --> 0:16:30.520
<v Speaker 6>antarcticas or the deserts. We're might to be power, but

0:16:30.640 --> 0:16:33.240
<v Speaker 6>no people or no no users or no customers. So

0:16:33.240 --> 0:16:35.160
<v Speaker 6>so we tend to still have to follow where our

0:16:35.200 --> 0:16:38.080
<v Speaker 6>products want to be. And and then within those you

0:16:38.120 --> 0:16:40.920
<v Speaker 6>know regions or those uber regions we have to we

0:16:40.960 --> 0:16:42.680
<v Speaker 6>have to go then you know, find power availability.

0:16:42.920 --> 0:16:46.960
<v Speaker 2>So okay, great, and Stephen, you you have great insight

0:16:47.040 --> 0:16:50.520
<v Speaker 2>into the entire kind of data center supply chain in

0:16:50.560 --> 0:16:53.920
<v Speaker 2>your ola Schneider, I'm interested, do you have any kind

0:16:53.920 --> 0:16:56.480
<v Speaker 2>of sense of how much of this new data build,

0:16:56.560 --> 0:17:00.680
<v Speaker 2>data center build that we're seeing is specifically I related.

0:17:00.800 --> 0:17:02.680
<v Speaker 2>Is that even something that makes sense? Is there an

0:17:02.720 --> 0:17:05.280
<v Speaker 2>AI data center versus something else or is it just bits?

0:17:05.440 --> 0:17:08.639
<v Speaker 5>Absolutely, the you know, the servers are completely different, and

0:17:08.880 --> 0:17:10.600
<v Speaker 5>you know, the power and the cooling is different. And

0:17:10.800 --> 0:17:12.440
<v Speaker 5>if you look at a data center, it's an AI

0:17:12.560 --> 0:17:14.920
<v Speaker 5>data center today, say it's a ten megawaut data center.

0:17:15.359 --> 0:17:17.040
<v Speaker 5>You know, five or six years ago, there'll be a

0:17:17.080 --> 0:17:19.600
<v Speaker 5>thousand IT racks and the data hall would be huge.

0:17:19.760 --> 0:17:21.920
<v Speaker 5>Now the data hall has seven d I t racks

0:17:21.960 --> 0:17:24.639
<v Speaker 5>and you have all these chillers outside, you know, to

0:17:24.680 --> 0:17:27.679
<v Speaker 5>support the cooling that so it's much different. It's not

0:17:27.760 --> 0:17:29.600
<v Speaker 5>these Amazon warehouse type data centers.

0:17:29.720 --> 0:17:29.880
<v Speaker 6>More.

0:17:29.920 --> 0:17:33.280
<v Speaker 5>There's smaller, more confined in the IT rooms, a lot

0:17:33.320 --> 0:17:35.159
<v Speaker 5>of power and cooling going through it. It's not a

0:17:35.200 --> 0:17:37.560
<v Speaker 5>place that you know, it used to be walk around

0:17:37.560 --> 0:17:39.439
<v Speaker 5>and you know your place, servers and everyone had a

0:17:39.440 --> 0:17:42.520
<v Speaker 5>good time, but not anymore. It's a it's a business.

0:17:42.840 --> 0:17:45.560
<v Speaker 5>But you know, as we were saying, you know, the

0:17:45.880 --> 0:17:49.919
<v Speaker 5>you know, putting an asset where there's where there's power,

0:17:49.920 --> 0:17:52.639
<v Speaker 5>and everybody in the world right now is saying that

0:17:52.640 --> 0:17:54.200
<v Speaker 5>the data centers are going to go where.

0:17:54.040 --> 0:17:54.639
<v Speaker 3>The power is.

0:17:54.680 --> 0:17:57.600
<v Speaker 5>But but what we're what we're seeing and the hyper

0:17:57.600 --> 0:18:00.439
<v Speaker 5>scales are all doing this as you just said, is

0:18:00.560 --> 0:18:05.119
<v Speaker 5>they're they're building these training clusters that are close to

0:18:05.320 --> 0:18:08.480
<v Speaker 5>where people are with the intention of using those to

0:18:08.520 --> 0:18:10.840
<v Speaker 5>make money. There's not a lot of money being made,

0:18:11.320 --> 0:18:13.760
<v Speaker 5>you know, training a model, and the question is how

0:18:13.760 --> 0:18:15.360
<v Speaker 5>many more of these models are we going to need,

0:18:15.840 --> 0:18:17.800
<v Speaker 5>so the money is going to be made and deploying

0:18:17.840 --> 0:18:20.560
<v Speaker 5>them in the field. And we're seeing a big shift

0:18:20.640 --> 0:18:22.960
<v Speaker 5>and this, in my opinion, is kind of the year

0:18:22.960 --> 0:18:26.040
<v Speaker 5>of infernts and and we're starting to see you know

0:18:26.520 --> 0:18:29.640
<v Speaker 5>a lot of these training clusters that were originally deployed

0:18:29.720 --> 0:18:32.640
<v Speaker 5>just to train are now doing infrints, either full time

0:18:32.920 --> 0:18:35.480
<v Speaker 5>or part time. And the other thing that we're seeing

0:18:35.560 --> 0:18:38.760
<v Speaker 5>is you know, with infrints close to the users, optimized

0:18:38.760 --> 0:18:41.840
<v Speaker 5>for different applications. We're not seeing those yet because AI

0:18:41.960 --> 0:18:44.120
<v Speaker 5>is still developing. We're still at the beginning of this.

0:18:44.359 --> 0:18:47.320
<v Speaker 5>We don't know, you know, what it's going to take

0:18:47.640 --> 0:18:50.320
<v Speaker 5>to do an AI agent and a genta AI. You

0:18:50.320 --> 0:18:51.639
<v Speaker 5>know what's that going to take. It's going to be

0:18:51.720 --> 0:18:54.440
<v Speaker 5>multi modal how much processing, how much how much of

0:18:54.480 --> 0:18:56.520
<v Speaker 5>the IT stack is going to be needed and where,

0:18:56.920 --> 0:19:00.040
<v Speaker 5>and as we start inputting more and more video. You

0:19:00.640 --> 0:19:03.400
<v Speaker 5>right now everything's text to text, you know, multimodal, it's

0:19:03.400 --> 0:19:05.280
<v Speaker 5>going to be video, tech, text, image, it's going to

0:19:05.359 --> 0:19:08.680
<v Speaker 5>be all these different things. So we can't optimize the

0:19:09.440 --> 0:19:12.360
<v Speaker 5>data centers close to the users yet for inference, we're

0:19:12.400 --> 0:19:14.520
<v Speaker 5>still going to have to do those in data centers.

0:19:14.800 --> 0:19:17.119
<v Speaker 5>I think that's going to be the case for a

0:19:17.119 --> 0:19:17.960
<v Speaker 5>few years.

0:19:18.480 --> 0:19:21.840
<v Speaker 2>Okay, so things not really changing too dramatically. It's just

0:19:21.880 --> 0:19:23.800
<v Speaker 2>build close to the users, like always.

0:19:25.480 --> 0:19:25.920
<v Speaker 3>So clever.

0:19:25.960 --> 0:19:28.400
<v Speaker 2>Actually, something I want to ask you about. I'm from

0:19:28.400 --> 0:19:30.680
<v Speaker 2>Ireland and so when I hear data center, I think,

0:19:30.720 --> 0:19:34.040
<v Speaker 2>oh my god, it's destroying the power system. There's like

0:19:34.119 --> 0:19:36.399
<v Speaker 2>moratorium and new data centers there because it's such a

0:19:36.440 --> 0:19:38.840
<v Speaker 2>large share of the power system. And there's a couple

0:19:38.880 --> 0:19:40.720
<v Speaker 2>of reasons in Europe where something like this has happened,

0:19:40.920 --> 0:19:43.840
<v Speaker 2>and now there's been conversations about this. This is going to

0:19:43.840 --> 0:19:46.160
<v Speaker 2>happen in the United States. Kind of seems like that's

0:19:46.200 --> 0:19:48.199
<v Speaker 2>calm down in the last few months. But interested to

0:19:48.240 --> 0:19:51.440
<v Speaker 2>hear your thoughts on how big a challenge this will

0:19:51.480 --> 0:19:53.200
<v Speaker 2>be for your business.

0:19:54.080 --> 0:19:56.800
<v Speaker 7>It's hard to talk about that without politicizing things. But

0:19:58.400 --> 0:20:01.879
<v Speaker 7>I think, look, there will be parts of the country

0:20:01.920 --> 0:20:05.359
<v Speaker 7>where there's there would be some resistance uh to data

0:20:05.400 --> 0:20:07.879
<v Speaker 7>center deployment. We are seeing some of that in the

0:20:08.200 --> 0:20:12.800
<v Speaker 7>Southeast and other and other parts. I think I think

0:20:12.840 --> 0:20:15.800
<v Speaker 7>it's the real answer to that is all going to

0:20:15.880 --> 0:20:20.080
<v Speaker 7>depend on the solutions that we bring to to that

0:20:20.240 --> 0:20:21.760
<v Speaker 7>data center load growth.

0:20:21.800 --> 0:20:23.800
<v Speaker 3>When you say we, do you mean as or do

0:20:23.840 --> 0:20:24.480
<v Speaker 3>you mean we.

0:20:24.680 --> 0:20:30.760
<v Speaker 7>The providers of energy and together with the data center

0:20:30.840 --> 0:20:33.840
<v Speaker 7>operators and the and the hyper skaters. I think a

0:20:33.840 --> 0:20:36.080
<v Speaker 7>lot of all we talked about here is that there

0:20:36.160 --> 0:20:39.080
<v Speaker 7>was a there was a time not long ago, there

0:20:39.320 --> 0:20:41.920
<v Speaker 7>was this idea that not because of the l LAM

0:20:42.160 --> 0:20:46.040
<v Speaker 7>training phase, a lot of data centers, large data centers

0:20:46.040 --> 0:20:51.160
<v Speaker 7>will co locate with generation in places where there's as

0:20:51.200 --> 0:20:53.920
<v Speaker 7>Will was saying, there's no load, that there's no infrastructure,

0:20:53.960 --> 0:20:57.320
<v Speaker 7>there's no fiber offs so you have to make up

0:20:57.359 --> 0:21:01.480
<v Speaker 7>for the lack of all that with low cost of power.

0:21:01.520 --> 0:21:04.159
<v Speaker 7>But when you when you when when you look at

0:21:04.359 --> 0:21:07.679
<v Speaker 7>the amount of capital that in you to deploy in

0:21:07.760 --> 0:21:10.280
<v Speaker 7>those data centers, you don't want to run the risk

0:21:10.720 --> 0:21:14.719
<v Speaker 7>of being stranded after the training phase of the of

0:21:14.760 --> 0:21:19.120
<v Speaker 7>the large language model uh ends, so you want to

0:21:19.200 --> 0:21:22.840
<v Speaker 7>use that for something else. So we talked a lot

0:21:22.840 --> 0:21:25.720
<v Speaker 7>about this that here you end up going back to

0:21:26.320 --> 0:21:29.439
<v Speaker 7>where the traditional data center markets are, and in some

0:21:29.520 --> 0:21:32.760
<v Speaker 7>of those markets we are seeing local resistance.

0:21:33.000 --> 0:21:33.359
<v Speaker 3>Uh.

0:21:33.600 --> 0:21:38.760
<v Speaker 7>We're also seeing local resistance to the development of power

0:21:38.800 --> 0:21:43.440
<v Speaker 7>plants to supply those those data centers. The famous NIM

0:21:43.480 --> 0:21:46.199
<v Speaker 7>business not in my backyard. So I think that is

0:21:46.240 --> 0:21:49.680
<v Speaker 7>a challenge that that the industry, both the energy industry

0:21:50.040 --> 0:21:53.960
<v Speaker 7>and the data center industry, has to overcome. It is

0:21:54.000 --> 0:21:57.920
<v Speaker 7>a real challenge, uh. And I think it's one that

0:21:58.240 --> 0:22:02.200
<v Speaker 7>will be will be met with deployment of transmission, because

0:22:03.119 --> 0:22:05.919
<v Speaker 7>I think that there's more flexibility where you can deploy

0:22:06.040 --> 0:22:08.480
<v Speaker 7>data centers than there will be on where you deploy

0:22:09.160 --> 0:22:14.040
<v Speaker 7>the generation, whether it's gas or or renewable. I hopefully

0:22:14.119 --> 0:22:17.280
<v Speaker 7>we don't get to new coal to supply to supply

0:22:17.400 --> 0:22:22.080
<v Speaker 7>this demand. And the bottomneck here is actually transmission to

0:22:22.160 --> 0:22:25.679
<v Speaker 7>get to from from from the generational sources to the

0:22:26.080 --> 0:22:27.240
<v Speaker 7>to the data centers.

0:22:27.720 --> 0:22:30.920
<v Speaker 2>Okay, and we'll actually going to ask you about Google

0:22:31.000 --> 0:22:34.560
<v Speaker 2>has been quite active on trying to develop new sources

0:22:34.600 --> 0:22:39.560
<v Speaker 2>of clean energy before actually this whole AI drive became

0:22:39.600 --> 0:22:42.560
<v Speaker 2>a thing, but you signed a couple of pretty first

0:22:42.560 --> 0:22:44.440
<v Speaker 2>of a kind PPAs in the last couple of years.

0:22:44.480 --> 0:22:47.680
<v Speaker 2>It'd be interesting to hear how progress in that is developing.

0:22:47.840 --> 0:22:48.040
<v Speaker 3>Yeah.

0:22:48.119 --> 0:22:52.760
<v Speaker 6>Sure, So the history of you know, energy consumption and

0:22:52.840 --> 0:22:55.760
<v Speaker 6>energy generation Google is a long one. But the short

0:22:55.760 --> 0:22:58.119
<v Speaker 6>story is this, since I've been there last you know,

0:22:58.200 --> 0:23:00.360
<v Speaker 6>ten and a half yars or so, are our energy

0:23:00.359 --> 0:23:03.240
<v Speaker 6>consumption globally has grown between twenty twenty five percent a year.

0:23:04.080 --> 0:23:07.840
<v Speaker 6>We're now approaching thirty plus maybe more tearrawad hours of

0:23:08.000 --> 0:23:11.879
<v Speaker 6>energy you know, consumed every year. That's doubling every you know,

0:23:12.000 --> 0:23:15.480
<v Speaker 6>five years or so. And we've also signed you know,

0:23:17.000 --> 0:23:20.600
<v Speaker 6>you know, twenty plus gigawatts of renewable energy generation you know,

0:23:20.680 --> 0:23:24.720
<v Speaker 6>contracts to with folks like A Yes and others to

0:23:24.720 --> 0:23:29.280
<v Speaker 6>to help supply energy to our facilities. We we maintain

0:23:29.400 --> 0:23:32.160
<v Speaker 6>a strong climent to our to our clean energy goals,

0:23:32.160 --> 0:23:35.960
<v Speaker 6>and we have an hourly carbon free energy goal a

0:23:35.960 --> 0:23:38.879
<v Speaker 6>BYT twenty thirty that we continue to chase and uh

0:23:39.080 --> 0:23:41.439
<v Speaker 6>chase very vigorously and and to that end, you know,

0:23:41.480 --> 0:23:44.520
<v Speaker 6>we The story there is you can get to about

0:23:44.520 --> 0:23:47.560
<v Speaker 6>seventy to eighty percent carbon free and energy supplies you know,

0:23:47.800 --> 0:23:51.719
<v Speaker 6>through wind and solar and batteries and sort of like

0:23:51.800 --> 0:23:55.159
<v Speaker 6>the mix of things there. But that last twenty to

0:23:55.160 --> 0:23:58.640
<v Speaker 6>twenty five percent, that last mile is is harder because

0:23:58.640 --> 0:24:00.919
<v Speaker 6>you have to start thinking about capacity and baseload and

0:24:00.920 --> 0:24:03.640
<v Speaker 6>reliability and this sort of stuff. And so we spent

0:24:03.680 --> 0:24:06.040
<v Speaker 6>the last few years thinking about and working on, you know,

0:24:06.119 --> 0:24:09.400
<v Speaker 6>sort of what are those next gen technologies after wind

0:24:09.400 --> 0:24:11.119
<v Speaker 6>and solar that are going to be carbon free and

0:24:11.680 --> 0:24:14.840
<v Speaker 6>start to supply you know, up to that that nearly

0:24:14.840 --> 0:24:17.359
<v Speaker 6>one hundred percent carbon free energy. And for US, it's

0:24:17.400 --> 0:24:22.200
<v Speaker 6>things like nuclear power, it's things like launderation storage, it's

0:24:22.400 --> 0:24:26.600
<v Speaker 6>potentially hydrogen, don't look too hard. It's potentially like carbon

0:24:26.640 --> 0:24:30.800
<v Speaker 6>capture and storage and geothermal and we've done a couple

0:24:30.880 --> 0:24:32.360
<v Speaker 6>of these in the last couple of years. We did

0:24:32.520 --> 0:24:35.639
<v Speaker 6>a deal in Nevada between US and a company called Ferbo,

0:24:36.080 --> 0:24:39.560
<v Speaker 6>who's a geothermal developer. They're using our cloud technology to

0:24:39.840 --> 0:24:42.000
<v Speaker 6>optimize how they drill wells and operate their wells and

0:24:42.000 --> 0:24:45.800
<v Speaker 6>operate their plants to then build advanced geothermal plants to

0:24:45.960 --> 0:24:49.800
<v Speaker 6>sell that power to Novada Energy, the utility with whom

0:24:49.880 --> 0:24:52.280
<v Speaker 6>We designed a tariff for a new rate that the

0:24:52.359 --> 0:24:56.080
<v Speaker 6>regulator is approving that's gonna a sign or a lot

0:24:56.240 --> 0:24:58.880
<v Speaker 6>allocate the costs of that geothermal above and beyond sort

0:24:58.880 --> 0:25:01.639
<v Speaker 6>of business as usual to us, the customer right so

0:25:01.680 --> 0:25:03.760
<v Speaker 6>that we don't so that we get the product we want,

0:25:03.840 --> 0:25:07.240
<v Speaker 6>the grid gets a clean baseload generation source, and other

0:25:07.280 --> 0:25:10.240
<v Speaker 6>right pairers don't don't pay the cost. So that's what

0:25:10.320 --> 0:25:12.119
<v Speaker 6>we're really proud of. And that's a model, you know,

0:25:12.240 --> 0:25:14.840
<v Speaker 6>that sort of rate structure and that you can slot

0:25:14.880 --> 0:25:17.560
<v Speaker 6>different technologies into is a model we're working on with

0:25:17.600 --> 0:25:20.679
<v Speaker 6>a lot of other utilities across the US. And then

0:25:20.720 --> 0:25:23.639
<v Speaker 6>the other is a partnership we recently as signed with

0:25:23.680 --> 0:25:28.640
<v Speaker 6>a small modular reactor technology provider called Chiros Power. Chiros

0:25:28.720 --> 0:25:32.320
<v Speaker 6>is developing Gen four small monulor reactors. They have a

0:25:32.320 --> 0:25:35.119
<v Speaker 6>pilot planned for twenty twenty nine for which we're going

0:25:35.160 --> 0:25:38.479
<v Speaker 6>to be a customer in the Tennessee Valley. And in

0:25:38.520 --> 0:25:40.400
<v Speaker 6>addition to being a customer for the pilot to help

0:25:40.400 --> 0:25:43.080
<v Speaker 6>get that commercialized and off the ground, we committed to

0:25:43.119 --> 0:25:46.320
<v Speaker 6>being a customer for their next five reactors. And what

0:25:46.320 --> 0:25:49.880
<v Speaker 6>we get out of that is, you know, some confidence

0:25:49.920 --> 0:25:52.680
<v Speaker 6>of having access to power, assuming that everything goes well

0:25:52.680 --> 0:25:54.639
<v Speaker 6>with our technology, but also the ability to sort of

0:25:54.960 --> 0:25:58.199
<v Speaker 6>partner with them to cite those next reactors in places

0:25:58.200 --> 0:26:00.280
<v Speaker 6>that you know, hopefully make make sense for us and

0:26:00.280 --> 0:26:02.560
<v Speaker 6>our loads and our data centers to then meet that

0:26:02.600 --> 0:26:05.200
<v Speaker 6>hourly carbon free energy goal in places we have growing load.

0:26:05.280 --> 0:26:08.639
<v Speaker 6>And so we expect in the twenty thirties to be

0:26:08.800 --> 0:26:12.199
<v Speaker 6>deploying small modulor reactors onto the grid. It's not going

0:26:12.240 --> 0:26:14.800
<v Speaker 6>to be like a you know, Antarctica small modul the

0:26:14.840 --> 0:26:17.040
<v Speaker 6>actor of data center behind the meter microgrid thing. That's

0:26:17.080 --> 0:26:19.880
<v Speaker 6>not the plan. It's really meant to be a grid

0:26:19.920 --> 0:26:23.360
<v Speaker 6>participant and putting capacity on the grid to supply our needs.

0:26:23.440 --> 0:26:25.400
<v Speaker 6>And so Bi you said about that as well.

0:26:25.560 --> 0:26:26.680
<v Speaker 3>Yeah, okay, great.

0:26:27.160 --> 0:26:30.040
<v Speaker 2>So something someone alluded to earlier was the topic of

0:26:30.200 --> 0:26:34.400
<v Speaker 2>energy efficiency and the word deep seek, which hads.

0:26:34.240 --> 0:26:34.639
<v Speaker 3>Up in the room.

0:26:34.680 --> 0:26:36.399
<v Speaker 2>Does everyone know like what I'm referring to when I

0:26:36.400 --> 0:26:41.680
<v Speaker 2>talk about deep seek? Yes, okay, great, darsh I'm gonna

0:26:41.680 --> 0:26:44.399
<v Speaker 2>go to you here because we're having a conversation whether

0:26:45.560 --> 0:26:48.800
<v Speaker 2>this this something that everyone saw coming. Not necessarily the

0:26:48.880 --> 0:26:50.919
<v Speaker 2>idea that like deep seek was going to release a

0:26:50.920 --> 0:26:53.080
<v Speaker 2>model and this would be the exact market reaction, but

0:26:54.200 --> 0:26:56.640
<v Speaker 2>that there was going to be big gains in energy

0:26:56.640 --> 0:26:59.120
<v Speaker 2>efficiency improvements. This has obviously been the history of data

0:26:59.119 --> 0:27:02.200
<v Speaker 2>centers for ages that energy efficiency has improved. So like,

0:27:02.240 --> 0:27:04.960
<v Speaker 2>why were people so surprised by this? And what's the

0:27:04.960 --> 0:27:09.480
<v Speaker 2>future of energy efficiency in artificial intelligence? Simple question if.

0:27:09.400 --> 0:27:13.560
<v Speaker 3>You could just do great question.

0:27:15.119 --> 0:27:17.720
<v Speaker 4>I think technology comes in waves where like you make

0:27:17.800 --> 0:27:20.520
<v Speaker 4>really good hardware and then you try to extract performance

0:27:20.520 --> 0:27:22.359
<v Speaker 4>out of the hardware as much you can. When you

0:27:22.400 --> 0:27:25.000
<v Speaker 4>reach the limit of what you can do in software space,

0:27:25.040 --> 0:27:27.560
<v Speaker 4>you go back and make better hardware. And ideally that's

0:27:27.600 --> 0:27:29.960
<v Speaker 4>like a very quick trend of like, hey, I spent

0:27:30.040 --> 0:27:32.480
<v Speaker 4>six months, let's say one to two years making hardware,

0:27:33.040 --> 0:27:35.160
<v Speaker 4>one to two years making software, and then I find

0:27:35.160 --> 0:27:36.920
<v Speaker 4>the holes in the hardware and I make it better. Right,

0:27:37.600 --> 0:27:39.600
<v Speaker 4>So I think, what I think, it's just more mostly

0:27:39.600 --> 0:27:41.840
<v Speaker 4>timing like this happened now, I think, yeah, this is

0:27:41.880 --> 0:27:44.320
<v Speaker 4>the expectation is that, hey, I can only buy a

0:27:44.359 --> 0:27:46.720
<v Speaker 4>certain number of Vida GPUs. What can I do with this?

0:27:46.800 --> 0:27:47.080
<v Speaker 3>Now?

0:27:48.000 --> 0:27:52.680
<v Speaker 4>Let me hire highly specialized PTX programmers that don't write

0:27:52.720 --> 0:27:55.840
<v Speaker 4>Kuda code. They right level below that because Kuda doesn't

0:27:55.880 --> 0:27:58.320
<v Speaker 4>solve the problem that I needed to solve. It's too abstracted,

0:27:58.359 --> 0:28:01.120
<v Speaker 4>it too, it's too power hungry, right, so I don't

0:28:01.119 --> 0:28:03.159
<v Speaker 4>get I don't get enough control over the hardware, so

0:28:03.200 --> 0:28:05.240
<v Speaker 4>I need to go to a lower level. You keep

0:28:05.240 --> 0:28:07.520
<v Speaker 4>going down that stack. You get down to hardware, then

0:28:07.520 --> 0:28:09.159
<v Speaker 4>you go down, you go to TSMC, right, then you

0:28:09.200 --> 0:28:11.840
<v Speaker 4>go down you get to like minerals and things like that.

0:28:11.920 --> 0:28:14.119
<v Speaker 3>So you can keep going down that stack.

0:28:14.200 --> 0:28:18.040
<v Speaker 4>But definitely, I think what Deep Sea proved and if

0:28:18.040 --> 0:28:20.359
<v Speaker 4>you guys with the pre the paper, the last page,

0:28:20.400 --> 0:28:24.280
<v Speaker 4>there's suggestions on how to improve in Vida GPUs, which

0:28:24.320 --> 0:28:28.439
<v Speaker 4>is really interesting because this is a redesigning them how

0:28:28.480 --> 0:28:30.440
<v Speaker 4>to use them. Yeah, the micro architecture of the Vida

0:28:30.520 --> 0:28:33.960
<v Speaker 4>GPUs is not optimal for what deep SEEQ wants basically,

0:28:34.680 --> 0:28:37.560
<v Speaker 4>which is interesting, right because that's the that's the cycle

0:28:37.600 --> 0:28:40.640
<v Speaker 4>we're going to go through and so not related. But

0:28:40.880 --> 0:28:44.080
<v Speaker 4>you know, the gp that we're designing solves those problems.

0:28:44.120 --> 0:28:46.280
<v Speaker 4>We did our own benchmarks three years ago and we

0:28:46.320 --> 0:28:47.920
<v Speaker 4>found out some of the problems that Deep Sea found

0:28:47.960 --> 0:28:51.760
<v Speaker 4>out as well. So there are ways to improve hardware honestly,

0:28:51.920 --> 0:28:55.280
<v Speaker 4>like the vendor should do you know, benchmarking and research

0:28:55.320 --> 0:28:57.520
<v Speaker 4>and make the GPUs better themselves. But yeah, it does

0:28:57.560 --> 0:29:01.960
<v Speaker 4>require some interactivity with and end user that's like, hey,

0:29:02.000 --> 0:29:04.120
<v Speaker 4>I want this to be better. Here's like four things

0:29:04.160 --> 0:29:05.840
<v Speaker 4>you can do to make it better. And that will

0:29:05.880 --> 0:29:09.000
<v Speaker 4>continue happening, right. People will make new GPUs, new accelerators,

0:29:10.000 --> 0:29:12.080
<v Speaker 4>people will make co package optics, they'll do all sorts

0:29:12.120 --> 0:29:14.760
<v Speaker 4>of fancy stuff and people will use it. But like,

0:29:14.760 --> 0:29:16.600
<v Speaker 4>I'd actually don't like the way this is running. It's

0:29:16.600 --> 0:29:18.480
<v Speaker 4>actually too slow for my use case. Can you fix

0:29:18.520 --> 0:29:20.080
<v Speaker 4>this thing? So I think this is like normal, but

0:29:20.600 --> 0:29:23.480
<v Speaker 4>I think there's so much focus on the volume of

0:29:23.560 --> 0:29:25.880
<v Speaker 4>GPU ship that I think people forgot that there's still

0:29:25.920 --> 0:29:28.760
<v Speaker 4>optimization room. There's a lot of headroom and optimizing software

0:29:28.800 --> 0:29:29.080
<v Speaker 4>for that.

0:29:29.800 --> 0:29:32.400
<v Speaker 2>Okay, how do you how does that kind of coordination

0:29:32.520 --> 0:29:36.160
<v Speaker 2>work between the software developers and a video like is there?

0:29:37.120 --> 0:29:39.040
<v Speaker 2>Do they have channels to work on this together? Doing

0:29:39.120 --> 0:29:42.000
<v Speaker 2>video have their own internal research teams? Yeah, it's called

0:29:42.040 --> 0:29:44.840
<v Speaker 2>hardware software code design. Some companies do it much better

0:29:44.880 --> 0:29:49.680
<v Speaker 2>than others. We do it the best. Yeah, we do

0:29:49.680 --> 0:29:50.120
<v Speaker 2>a good job.

0:29:50.160 --> 0:29:52.880
<v Speaker 4>But yeah, no, they have teams internally that are building

0:29:52.920 --> 0:29:56.720
<v Speaker 4>fundational models at video train them on supercomputers, AI clusters

0:29:57.160 --> 0:29:59.720
<v Speaker 4>and then they're finding these things. But I think it's

0:29:59.760 --> 0:30:02.320
<v Speaker 4>interest that, Like your next question is, well, why didn't

0:30:02.320 --> 0:30:03.960
<v Speaker 4>they find this out, you know last year when they

0:30:04.040 --> 0:30:06.320
<v Speaker 4>made the hardware, Well, it's the same thing. Why is

0:30:06.320 --> 0:30:08.160
<v Speaker 4>black WU one hundred three to two kilowats per wack

0:30:08.160 --> 0:30:09.720
<v Speaker 4>instead of one hundred and twenty five? So there are

0:30:09.760 --> 0:30:13.160
<v Speaker 4>like there are fuzzy zones where you can miss things,

0:30:13.200 --> 0:30:15.320
<v Speaker 4>and I'm sure I'll miss things and it happens. But

0:30:15.840 --> 0:30:20.400
<v Speaker 4>I think the magnitude of that coming out so aggressively

0:30:20.440 --> 0:30:22.600
<v Speaker 4>saying hey, we don't need this much computing power. And

0:30:22.640 --> 0:30:24.880
<v Speaker 4>also there are things in the GPU at the micro

0:30:24.920 --> 0:30:27.240
<v Speaker 4>architecture level in the silicon that I don't like that

0:30:27.320 --> 0:30:28.200
<v Speaker 4>I want you to change.

0:30:28.240 --> 0:30:30.360
<v Speaker 3>Is is a step shift because.

0:30:30.160 --> 0:30:33.120
<v Speaker 4>Now you're expecting every customer to go down to that level.

0:30:33.160 --> 0:30:34.640
<v Speaker 4>And I think that's the race now as to how

0:30:35.240 --> 0:30:38.320
<v Speaker 4>optimized can you get with one water one hundred watts

0:30:38.400 --> 0:30:41.080
<v Speaker 4>or one giga water or whatever?

0:30:41.600 --> 0:30:43.040
<v Speaker 2>Do you have a kind of benchmark in your own

0:30:43.040 --> 0:30:46.640
<v Speaker 2>mind internally of this is the energy standard that like

0:30:47.680 --> 0:30:50.680
<v Speaker 2>a query and chat GPT was a year ago. How

0:30:50.800 --> 0:30:52.840
<v Speaker 2>much more energy efficient can we get? That? Is it

0:30:53.000 --> 0:30:54.040
<v Speaker 2>orders of magnitude or.

0:30:54.080 --> 0:30:56.120
<v Speaker 3>Orders of magnitude orders of magnitude.

0:30:56.120 --> 0:30:59.000
<v Speaker 4>Absolutely, yeah, I think this conversation is good because everyone

0:30:59.040 --> 0:31:01.760
<v Speaker 4>in the panels like it. Will we're delivering power, that's great,

0:31:01.880 --> 0:31:04.600
<v Speaker 4>that's a problem. But also like I'm a chip guy,

0:31:04.680 --> 0:31:07.240
<v Speaker 4>like we should make better chips that consume less power.

0:31:07.640 --> 0:31:10.640
<v Speaker 4>Perhaps maybe there's like a push and pulled balance there

0:31:10.640 --> 0:31:12.200
<v Speaker 4>of you know, like keep using a good job. Right,

0:31:12.200 --> 0:31:15.520
<v Speaker 4>that's orders of magnitude less, less power consumption, more efficient

0:31:15.520 --> 0:31:17.880
<v Speaker 4>than and envita GPU. It is the main specific in

0:31:17.880 --> 0:31:19.760
<v Speaker 4>that sense, but it does solve the problem and it's

0:31:19.760 --> 0:31:23.120
<v Speaker 4>more efficient. So you will see like a chip startups,

0:31:23.160 --> 0:31:26.440
<v Speaker 4>AI startups, quote package optic startups, all these all these

0:31:26.480 --> 0:31:30.120
<v Speaker 4>companies competing and being able to deliver much orders a

0:31:30.160 --> 0:31:31.280
<v Speaker 4>magnitude better efficiency.

0:31:31.320 --> 0:31:32.000
<v Speaker 3>That's what we're doing.

0:31:32.600 --> 0:31:35.000
<v Speaker 2>Okay, So for the three other panelists, I'm got to

0:31:35.000 --> 0:31:39.080
<v Speaker 2>ask you the same question is did you see this coming? Well? Actually, sorry,

0:31:39.120 --> 0:31:40.959
<v Speaker 2>The first question is how do you operate and like

0:31:41.160 --> 0:31:43.160
<v Speaker 2>you need to make these big decisions about what to

0:31:43.160 --> 0:31:46.640
<v Speaker 2>build and what to allocate resource to under this level

0:31:46.680 --> 0:31:49.600
<v Speaker 2>of uncertainty around energy efficiency improvements. But then I guess

0:31:49.640 --> 0:31:52.000
<v Speaker 2>the second part of the question is does everyone who

0:31:52.000 --> 0:31:54.480
<v Speaker 2>works in the industry kind of assume there's gonna be

0:31:54.520 --> 0:31:56.920
<v Speaker 2>these energy efficiency imrovements you're kind of making decisions around that.

0:31:57.360 --> 0:32:02.000
<v Speaker 5>So ho to you first student, I think everyone expected

0:32:02.160 --> 0:32:05.080
<v Speaker 5>more efficiencies to be to be gained in the transformers

0:32:05.080 --> 0:32:07.960
<v Speaker 5>and the algorithms and and but you know, I think

0:32:07.960 --> 0:32:09.960
<v Speaker 5>he had a panelist earlier that said, you know, all

0:32:10.080 --> 0:32:12.080
<v Speaker 5>the all the models that have been trained have been

0:32:12.080 --> 0:32:14.720
<v Speaker 5>trained on the public data, and there's all this other,

0:32:15.240 --> 0:32:17.920
<v Speaker 5>you know, private data that's actually going to be you know,

0:32:18.040 --> 0:32:21.240
<v Speaker 5>more beneficial. But all I can say about about that

0:32:21.480 --> 0:32:25.880
<v Speaker 5>is that it was this is probably the most confusing topic,

0:32:26.000 --> 0:32:28.680
<v Speaker 5>all the experts that are weighing in and saying completely

0:32:28.680 --> 0:32:33.920
<v Speaker 5>different things. But we haven't seen any reaction, negative reaction

0:32:34.080 --> 0:32:36.760
<v Speaker 5>from of our from our customers as far as you know.

0:32:36.840 --> 0:32:39.840
<v Speaker 3>Orders or or forecasts. It's all. It's all, you know,

0:32:39.920 --> 0:32:42.760
<v Speaker 3>business as usual. There's been like no effect at all.

0:32:43.080 --> 0:32:49.720
<v Speaker 6>Yeah, well, yeah, I think you know, Google and look,

0:32:50.040 --> 0:32:53.280
<v Speaker 6>training models and and and uh, software and hardware are

0:32:53.400 --> 0:32:55.960
<v Speaker 6>by no means my own expertise, and so so i'm

0:32:56.040 --> 0:32:58.280
<v Speaker 6>I'm I don't have a lot to offer here except

0:32:58.320 --> 0:33:01.120
<v Speaker 6>for I think we always expect deficiency gains. I think

0:33:01.120 --> 0:33:04.280
<v Speaker 6>we welcome them. I think we're seeing the same sort

0:33:04.320 --> 0:33:07.320
<v Speaker 6>of efficiency gains and our own you know, model building

0:33:07.360 --> 0:33:11.520
<v Speaker 6>and model training and uh and uh, you know that

0:33:11.720 --> 0:33:14.960
<v Speaker 6>it hasn't to See's point, it hasn't really changed our

0:33:15.120 --> 0:33:19.800
<v Speaker 6>look on on our on our business planning because training

0:33:19.840 --> 0:33:22.600
<v Speaker 6>is only part of you know, the AI story and

0:33:22.640 --> 0:33:26.640
<v Speaker 6>the machine learning story. The serving and the inferences is

0:33:26.360 --> 0:33:28.640
<v Speaker 6>A is also a big part of it. And and

0:33:28.760 --> 0:33:31.040
<v Speaker 6>you know, don't forget that Google does myriad other things

0:33:31.040 --> 0:33:33.040
<v Speaker 6>and data centers right, and so data center, so mL

0:33:33.080 --> 0:33:34.840
<v Speaker 6>and A I are are but a portion of our

0:33:35.280 --> 0:33:37.200
<v Speaker 6>of our forecast and our outlook, and so so we

0:33:37.320 --> 0:33:39.120
<v Speaker 6>remain sort of on a stalle path.

0:33:41.000 --> 0:33:42.800
<v Speaker 7>Yeah, I think the same thing here. I haven't seen

0:33:42.840 --> 0:33:47.200
<v Speaker 7>any real change perhaps with the with the small exception

0:33:47.280 --> 0:33:52.640
<v Speaker 7>of investors over reaction to to headlines, but but the

0:33:52.680 --> 0:33:55.480
<v Speaker 7>fundamentals of the business remain very strong. Let's not forget

0:33:55.520 --> 0:33:57.880
<v Speaker 7>here that a lot of what we're trying to solve

0:33:57.880 --> 0:34:03.560
<v Speaker 7>for in the power markets is also replacement of aging

0:34:03.760 --> 0:34:08.680
<v Speaker 7>infrastructure in the US, especially no cold generation gas generation.

0:34:09.360 --> 0:34:13.759
<v Speaker 7>So efficiency gains are definitely welcome because what that's going

0:34:13.840 --> 0:34:16.319
<v Speaker 7>to do is to make sure that we don't overbuild.

0:34:16.800 --> 0:34:19.000
<v Speaker 7>The worst thing that could happen here is if the

0:34:19.040 --> 0:34:26.040
<v Speaker 7>market starts overbuild, overbuilding generation, transmission, distribution, and rate payers

0:34:26.080 --> 0:34:30.120
<v Speaker 7>get left with massive bills and the demand doesn't show up, right,

0:34:30.160 --> 0:34:32.640
<v Speaker 7>that would be a cycle of boom and bus.

0:34:32.719 --> 0:34:32.839
<v Speaker 2>Right.

0:34:32.880 --> 0:34:36.040
<v Speaker 7>So we believe in competitive markets. We believe in market efficiency.

0:34:36.640 --> 0:34:41.400
<v Speaker 7>And I think if if the efficiency is on the on,

0:34:41.440 --> 0:34:44.080
<v Speaker 7>the on, the on the computing power, also if that

0:34:44.120 --> 0:34:47.839
<v Speaker 7>brings demand back to a more reasonable level. But no

0:34:47.880 --> 0:34:51.520
<v Speaker 7>matter what the projections are, the numbers are staggering. The

0:34:51.960 --> 0:34:55.480
<v Speaker 7>projections for demand for new generation and new and new

0:34:55.520 --> 0:34:59.720
<v Speaker 7>infrastructure for transmission are staggering. So we just hope that

0:34:59.719 --> 0:35:02.200
<v Speaker 7>that that we don't overbuild. I guess that's right.

0:35:02.239 --> 0:35:02.520
<v Speaker 3>Okay.

0:35:02.560 --> 0:35:04.719
<v Speaker 2>So I have one quick fire question which you're only

0:35:04.719 --> 0:35:08.000
<v Speaker 2>allowed to answer one number two by twenty thirty. What

0:35:08.160 --> 0:35:10.480
<v Speaker 2>percentage of US power demand do you think will come

0:35:10.520 --> 0:35:11.480
<v Speaker 2>from data centers?

0:35:12.320 --> 0:35:14.400
<v Speaker 3>Not no explanation, just a number.

0:35:15.040 --> 0:35:21.840
<v Speaker 2>There's a networking session after seven and a half, well SIXI.

0:35:21.440 --> 0:35:26.360
<v Speaker 7>Ish, yeah, I think I'm a little perhaps a little

0:35:26.400 --> 0:35:29.200
<v Speaker 7>more more bullish than that. I think it would be

0:35:29.200 --> 0:35:31.320
<v Speaker 7>like somewhere between eight and ten percent.

0:35:32.160 --> 0:35:36.239
<v Speaker 2>Okay, especially pretty clustered around a certain range. But thank

0:35:36.239 --> 0:35:38.600
<v Speaker 2>you very much. This is really informantive panel. I think

0:35:38.600 --> 0:35:41.680
<v Speaker 2>we learned a lot about the idea that the data

0:35:41.719 --> 0:35:44.359
<v Speaker 2>center industry is going to grow. We're very all, very

0:35:44.400 --> 0:35:47.279
<v Speaker 2>confident on that, but actually maybe won't change quite as

0:35:47.320 --> 0:35:51.440
<v Speaker 2>much in terms of its geographic structure or capital investment cycled.

0:35:51.920 --> 0:35:54.319
<v Speaker 2>So thank you very much for joining me. Please join

0:35:54.400 --> 0:35:55.920
<v Speaker 2>me and giving my Palels a round of applause.

0:36:06.760 --> 0:36:09.879
<v Speaker 1>Today's episode of Switched On was produced by Cam Gray

0:36:10.080 --> 0:36:13.759
<v Speaker 1>with production assistance from Kamala Shelling. Bloomberg NIF is a

0:36:13.800 --> 0:36:16.880
<v Speaker 1>service provided by Bloomberg Finance LP and its affiliates. This

0:36:17.000 --> 0:36:19.680
<v Speaker 1>recording does not constitute, nor should it be construed as

0:36:19.719 --> 0:36:23.480
<v Speaker 1>investment in vice, investment recommendations, or a recommendation as to

0:36:23.520 --> 0:36:26.360
<v Speaker 1>an investment or other strategy. Bloomberg ANIF should not be

0:36:26.440 --> 0:36:30.200
<v Speaker 1>considered as information sufficient upon which to base an investment decision.

0:36:30.320 --> 0:36:33.279
<v Speaker 1>Neither Bloomberg Finance LP nor any of its affiliates makes

0:36:33.320 --> 0:36:37.040
<v Speaker 1>any representation or warranty as to the accuracy or completeness

0:36:37.040 --> 0:36:40.040
<v Speaker 1>of the information contained in this recording, and any liability

0:36:40.080 --> 0:36:42.759
<v Speaker 1>as a result of this recording is expressly disclaimed,