WEBVTT

00:00:00.199 --> 00:00:07.280
ladies and gentlemen AMD has done it

00:00:03.919 --> 00:00:11.360
again the Epic Bergamo

00:00:07.280 --> 00:00:14.280
9754 crams 32 more cores into the

00:00:11.360 --> 00:00:22.599
already well stuffed sp5 package of Epic Genoa for a total of a whopping

00:00:18.480 --> 00:00:26.320
128 cores in the palm of my

00:00:22.599 --> 00:00:28.240
hand or is it yes it is but I can

00:00:26.320 --> 00:00:33.719
practically hear you guys furiously typing away lius who's going to spend

00:00:30.679 --> 00:00:36.399
$122,000 on a CPU I'm never going to use

00:00:33.719 --> 00:00:40.719
or even touch one of these monsters but here's the thing in the same way that

00:00:38.480 --> 00:00:45.239
the Technologies from multi-million dollar Formula 1 cars trickle down

00:00:42.960 --> 00:00:50.079
eventually to our daily drivers the advances that debut in high-end data

00:00:47.920 --> 00:00:55.559
center chips almost inevitably make their way into your home PC and there is

00:00:52.840 --> 00:01:01.519
a lot of goodness packed in here to be excited about and besides who cares if

00:00:58.320 --> 00:01:03.760
you ever need one holy sh it's a 128

00:01:01.519 --> 00:01:09.560
core CPU let's take this thing out for a rip rip like this segue to our sponsor

00:01:07.320 --> 00:01:13.600
ODU a great business needs a great website so make yours for free with

00:01:11.560 --> 00:01:17.560
odu's intuitive all-in-one business management software click the link below

00:01:16.000 --> 00:01:23.880
or watch till the end of the video to learn more to achieve this level of core

00:01:20.479 --> 00:01:26.360
stuffy AMD took the same impressive IO

00:01:23.880 --> 00:01:32.439
die found on their epic Genoa CPUs that we met last year and they reworked the

00:01:28.920 --> 00:01:35.600
ccds or core complex dieses for higher

00:01:32.439 --> 00:01:37.720
density I will not be popping the lid

00:01:35.600 --> 00:01:42.360
off of this thing to show you guys but if I did you would notice a couple of

00:01:39.640 --> 00:01:47.520
key things first is that in spite of the higher core count there are actually

00:01:44.200 --> 00:01:52.880
fewer ccds that's because instead of up

00:01:47.520 --> 00:01:55.439
to 128 core D we're looking at 8 16 core

00:01:52.880 --> 00:02:03.039
dies how on Earth did they pack them in so tight by using Zen 4C cores rather

00:01:59.320 --> 00:02:06.759
than Reg regular Zen 4 cores now Zen 4C

00:02:03.039 --> 00:02:09.119
is not like an Intel e or efficiency

00:02:06.759 --> 00:02:15.720
core it should have the same performance per clock and the same level of feature

00:02:11.640 --> 00:02:18.800
support just packed 1.5 squ mm tighter

00:02:15.720 --> 00:02:22.560
each this means up to

00:02:18.800 --> 00:02:25.280
256 cores in a 2p or two processor

00:02:22.560 --> 00:02:30.400
server but it does come at a cost you lose some clock speed and you lose some

00:02:28.120 --> 00:02:34.720
level three Cash which doesn't sound like a very good thing and is probably

00:02:32.360 --> 00:02:41.239
the second thing you'd notice because in spite of having 33% more cores than

00:02:37.400 --> 00:02:44.159
Genoa bergo ends up with only 66% as

00:02:41.239 --> 00:02:48.560
much level three cash now AMD's argument for this is that in a cloud native

00:02:46.920 --> 00:02:53.200
workload we're not expecting to overcommit core so it'll be less

00:02:50.680 --> 00:02:58.360
impactful than you think but what even is a cloud native workload I'm so glad

00:02:56.280 --> 00:03:02.680
you asked it's still a little vaguely defined but examples might be things you

00:03:00.680 --> 00:03:07.319
use every day like search and social media and also tools you might not

00:03:05.120 --> 00:03:12.120
realize you're using every day like software infrastructure and platform as

00:03:09.560 --> 00:03:16.200
a service providers so in a way that makes sense since each workload is

00:03:13.920 --> 00:03:21.040
likely to be contained to the core or maybe couple of cores that are allocated

00:03:18.120 --> 00:03:25.080
to it without as much sharing of cached data across the CPU enough about that

00:03:23.640 --> 00:03:30.480
though let's get this thing built starting with the motherboard which wow

00:03:28.200 --> 00:03:35.560
if you are into motherboards this is a really sexy one as I mentioned already

00:03:32.720 --> 00:03:40.799
bergo uses the same iio die as denoa which means there support for a whopping

00:03:37.439 --> 00:03:44.959
12 channels of DDR 5cc memory and as

00:03:40.799 --> 00:03:48.360
many as 128 Lanes of PCIe Gen 5 with a

00:03:44.959 --> 00:03:50.560
single processor or up to 160 with a

00:03:48.360 --> 00:03:55.360
dual processor setup and you can see evidence of that all over the ASRock

00:03:53.480 --> 00:04:00.200
Genova -2t

00:03:57.360 --> 00:04:04.799
x550 this thing is absolutely whistling with high-end features to the point

00:04:01.720 --> 00:04:07.680
where in spite of it being a wider deep

00:04:04.799 --> 00:04:12.159
Micro ATX form factor it doesn't even have room for everything that bergo has

00:04:10.040 --> 00:04:19.519
to offer I mean it doesn't help that the sp5 socket plus the accompanying vrm

00:04:15.400 --> 00:04:21.680
that can do anywhere from 360 to 400

00:04:19.519 --> 00:04:25.840
watts of power delivery takes up about a quarter of the board let's go ahead and

00:04:23.440 --> 00:04:29.160
get the CPU installed this is my first sp5 installed but on the surface it

00:04:27.600 --> 00:04:33.240
looks pretty similar to what we've seen with pre AMD Threadripper and epic

00:04:31.520 --> 00:04:41.199
processor so you lift up this carrier frame take out the cover man that is a

00:04:37.280 --> 00:04:41.199
lot of freaking pins

00:04:41.560 --> 00:04:47.120
6,096 really is that right that can't be

00:04:44.759 --> 00:04:53.800
right go ahead and count him we go ahead and Slot that guy in a

00:04:50.800 --> 00:04:55.800
little something like that really that's

00:04:53.800 --> 00:05:00.400
it you don't even have to torque down the CPU does the pressure come from the

00:04:58.080 --> 00:05:05.880
cooler yeah oh oh let's talk about that the reason

00:05:03.400 --> 00:05:09.800
these server CPUs have so many more pins than a consumer one is because of all

00:05:08.120 --> 00:05:14.000
the different endpoints that they need to be directly connected to and one of

00:05:12.000 --> 00:05:19.160
the biggest mechanical challenges with these platforms is making sure that

00:05:16.680 --> 00:05:24.120
every single one of them is contacting correctly because even one being missing

00:05:22.000 --> 00:05:29.000
you could have a memory stick not show up or a PCIe slot that stops working

00:05:27.319 --> 00:05:32.520
it's actually really common on Epic and thread rep builds especially if the

00:05:31.000 --> 00:05:36.680
installer either doesn't torque the screws down enough or doesn't torque

00:05:34.479 --> 00:05:43.479
them down in the right order as for the cooler we're using this is the xo4 sp5

00:05:40.960 --> 00:05:50.280
it was sent over by Silverstone and it looks surprisingly wimpy considering

00:05:46.400 --> 00:05:52.720
that it's cooling 128 CPU cores but

00:05:50.280 --> 00:05:58.520
because the heat sources the cores are spread over such a large area under this

00:05:55.520 --> 00:06:00.199
metal plate the IHS we don't have to

00:05:58.520 --> 00:06:06.479
worry about the same kinds of concentrated hot spots that you might

00:06:02.319 --> 00:06:08.240
see on something like an Intel 14900 K

00:06:06.479 --> 00:06:12.599
that means even the heat pipes that aren't dead center on the cooler can

00:06:10.400 --> 00:06:17.360
work much more efficiently and you can handle a 400 W CPU with a little thing

00:06:15.599 --> 00:06:22.560
like this the instructions call for anywhere from 10.8 to 13 ftlb of torque

00:06:20.280 --> 00:06:26.720
on each screw and for it to be tightened in a star pattern starting with the

00:06:24.599 --> 00:06:30.759
sides and then doing the diagonals one after the other of course if you want to

00:06:28.360 --> 00:06:34.800
be extra careful the best thing to do is start all the screws in that order and

00:06:32.560 --> 00:06:38.960
then do a second pass checking all of the torque values with that out of the

00:06:37.160 --> 00:06:44.800
way let's move on to the really cool stuff like RAM to help us take full

00:06:42.680 --> 00:06:53.599
advantage of this platform Micron sent over 12 96 gig sticks of ddr5 5600 which

00:06:50.680 --> 00:06:57.720
would give us a total of over a terabyte of memory if we could install all of

00:06:56.639 --> 00:07:02.000
them but unfortunately due to limit ation of this

00:06:59.960 --> 00:07:06.360
form factor we're only going to be able to put eight on it I know I'm as

00:07:04.840 --> 00:07:13.720
disappointed as you guys are that we're slumming it with 768 gigs of RAM but you

00:07:10.560 --> 00:07:15.879
know what I think we're going to be okay

00:07:13.720 --> 00:07:20.080
see look it's not so bad 8 channels of memory I actually think azrock has done

00:07:17.599 --> 00:07:26.199
a great job of maximizing the io given the limited space they're working with

00:07:21.720 --> 00:07:28.639
we have four full fat PCIe gen 5x6 slots

00:07:26.199 --> 00:07:33.800
down here so that's 64 of our lanes taken care of each of the larger mcio

00:07:31.639 --> 00:07:37.919
connectors here is another eight Lanes two of them also support these eight

00:07:35.680 --> 00:07:43.680
Port say a 6 gig breakout cables so that's 96 total now each of the m.2

00:07:40.960 --> 00:07:48.680
slots that's another four lanes and the same goes for the different

00:07:45.960 --> 00:07:56.080
MCI yeah this one right here so what's that 108 108 we're still 20 lanes shy

00:07:54.120 --> 00:08:02.800
maybe they did need a bigger motherboard AMD has described epic as being as much

00:07:59.599 --> 00:08:04.639
a PCIe switch as it is a CPU and they're

00:08:02.800 --> 00:08:08.159
really not kidding they've crammed as many expansion ports as they possibly

00:08:06.599 --> 00:08:11.960
could onto this board regardless of whether you'd actually be able to use

00:08:09.680 --> 00:08:17.240
all of it and we've still got 20 more PCIe Gen 5 Lanes swinging in the breeze

00:08:14.840 --> 00:08:22.280
we haven't even talked about the 8 PCI E gen 3 Lanes four of which are serving

00:08:19.560 --> 00:08:27.400
our dual 10 gig Nicks and one more going to our as 2600 remote management system

00:08:25.080 --> 00:08:32.000
that leaves three more Lanes just hanging out

00:08:30.280 --> 00:08:36.560
no one no one down the street okay doesn't matter down the

00:08:34.000 --> 00:08:41.479
street point is you toss in some minimal USB VGA port and we have a truly epic

00:08:40.039 --> 00:08:47.959
amount of IO anyone I don't I don't get the

00:08:45.120 --> 00:08:52.640
thing down the street I'm sorry we'll stop that now all that's left is to plug

00:08:50.160 --> 00:08:57.480
in some storage and figure out our power situation see I have no doubt that this

00:08:54.800 --> 00:09:01.120
15500 watt unit from Corsair can power the machine I'm just not sure sure how

00:08:59.560 --> 00:09:06.079
we're going to connect it you see there's no 24 pin power connector on

00:09:03.920 --> 00:09:11.120
here that would have taken up precious PCI Express and fan header space but

00:09:08.880 --> 00:09:16.320
that's okay slowly but surely the industry is moving away from the lower

00:09:13.480 --> 00:09:21.920
voltages that make up realistically most of the pins in a 24 pin connector and

00:09:18.560 --> 00:09:26.200
two 12vt only designs so what we've got

00:09:21.920 --> 00:09:28.279
instead is three 8 pin ATX CPU power

00:09:26.200 --> 00:09:33.440
connectors and then this tiny little four pin that takes an adapter off of

00:09:30.680 --> 00:09:38.360
your 24 pin just for the power switch that's the green and black one right

00:09:34.720 --> 00:09:39.959
here power okay and then 5vt standby

00:09:38.360 --> 00:09:44.480
which is going to allow you to wake the system with a USB device for example now

00:09:42.760 --> 00:09:48.880
I can practically hear you thinking wow that power supply is being comically

00:09:46.360 --> 00:09:54.040
underutilized but don't worry guys we're going to find something power hungry to

00:09:50.760 --> 00:09:56.399
plug into it that's foreshadowing but

00:09:54.040 --> 00:10:00.760
first putting this thing on a test bench feels like a bit of a disservice doesn't

00:09:58.120 --> 00:10:05.839
it I think we need need a case and I think I know just the

00:10:03.440 --> 00:10:12.320
one oh you're not getting that run are you dang

00:10:06.839 --> 00:10:15.160
it oh God what oh God this is awesome I

00:10:12.320 --> 00:10:21.040
give me a hand at this oh boy oh how much do the wheels cost surprisingly

00:10:17.720 --> 00:10:25.440
nothing they were included what is this

00:10:21.040 --> 00:10:28.760
okay this this is a piece of History the

00:10:25.440 --> 00:10:32.000
year was 2003 I had a lot less facial

00:10:28.760 --> 00:10:33.560
hair and had never experienced gaming on

00:10:32.000 --> 00:10:39.240
a dedicated GPU there's no clip for it YouTube

00:10:36.160 --> 00:10:41.720
hadn't been invented yet but AMD existed

00:10:39.240 --> 00:10:47.880
and was announcing their first fora into the workstation and server market up on

00:10:45.519 --> 00:10:53.399
this was also our first look at the 64-bit instruction set extension to x86

00:10:51.000 --> 00:10:58.000
that Intel would ultimately license and is still in use to this day AMD wanted

00:10:56.360 --> 00:11:02.720
to make a splash for the launch so they held an event down in in Texas and

00:10:59.959 --> 00:11:09.200
showed off a dozen prototype optron systems in everything from single CPU to

00:11:05.720 --> 00:11:12.240
eight CPU configurations all in cases

00:11:09.200 --> 00:11:15.079
just like this one complete with

00:11:12.240 --> 00:11:21.320
included wheel lock I love this pull out drawer too remember kitchy 5 and a/4 in

00:11:17.800 --> 00:11:22.600
devices this one's a speaker anyway

00:11:21.320 --> 00:11:26.160
after the event the systems were decommission so a bunch of them ended up

00:11:24.360 --> 00:11:31.320
being sold in a San Antonio computer store at least one ended up on eBay and

00:11:28.600 --> 00:11:35.920
several more were simply scrapped this one though was bought by fellow YouTuber

00:11:33.519 --> 00:11:40.440
Wolfman mods who put it in storage for several years before it eventually made

00:11:37.880 --> 00:11:46.040
its way up here now we've cleaned it up as much as we dare to but we don't

00:11:43.720 --> 00:11:52.760
really want to damage something so unique now this case not exactly

00:11:50.160 --> 00:11:58.920
designed for ATX motherboards but it's so big we can just toss our test bench

00:11:56.079 --> 00:12:02.519
inside it I think Perfection complete completely toolless installation oh

00:12:00.760 --> 00:12:06.200
other than the side panel but for that all we need is a quarter turn with our

00:12:04.320 --> 00:12:10.760
trusty LT screwdriver this is so janky how did

00:12:08.560 --> 00:12:17.880
they think this was a good idea how unexpected a graphics card haha hey

00:12:15.199 --> 00:12:24.040
we're booted 768 gigs of RAM and enough logical

00:12:21.680 --> 00:12:27.279
processors that it looks like a quad socket machine from just a couple of

00:12:26.480 --> 00:12:33.880
years ago did you see how how long that took

00:12:29.720 --> 00:12:36.880
to loan look at this list what this is

00:12:33.880 --> 00:12:40.680
absolutely mindblowing I mean okay it's

00:12:36.880 --> 00:12:44.240
only running at 1.8 GHz right now but 73

00:12:40.680 --> 00:12:46.000
7 75 Watts that seems pretty reasonable

00:12:44.240 --> 00:12:51.519
AMD's Radion division could take some notes they have desktop gpus that

00:12:47.880 --> 00:12:54.680
consume that at idol here we go how fast

00:12:51.519 --> 00:12:56.399
will this go remember guys this is R23

00:12:54.680 --> 00:12:59.399
not the older R20 this should put the burn

00:12:57.839 --> 00:13:02.959
on are you freaking kidding

00:13:04.600 --> 00:13:12.680
me one chip one chip it barely even

00:13:09.160 --> 00:13:16.680
managed to spool up we touched 235 Watts

00:13:12.680 --> 00:13:17.920
for 5 seconds maybe it was a fluke yeah

00:13:16.680 --> 00:13:21.839
yeah yeah maybe it was a fluke maybe it was a fluke try we'll try again we'll try

00:13:24.320 --> 00:13:29.240
again is it done right yeah I'd say

00:13:27.360 --> 00:13:34.839
maybe 2/3 of the core is actually got to 100 holy crap the rest just sat there

00:13:31.800 --> 00:13:37.240
like 70 wait we might not actually be

00:13:34.839 --> 00:13:43.120
using enough cores custom number of render threads

00:13:39.560 --> 00:13:45.680
256 can it go even faster than

00:13:43.120 --> 00:13:51.560
86,000 points it might have been using 256 it might just not have fully spooled

00:13:48.240 --> 00:13:53.519
up oh yeah there goes all your cores

00:13:51.560 --> 00:14:01.399
holy crap I think that was even 89,000 points guys context here okay a

00:13:57.720 --> 00:14:04.600
Threadripper 20 990 WX K that's a 32

00:14:01.399 --> 00:14:06.920
core chip is left completely in the dust

00:14:04.600 --> 00:14:11.560
but that's okay because Maxon has a new generation of cine bench

00:14:09.079 --> 00:14:15.839
r24 let's see if that can bring this monster to its knees I haven't actually

00:14:14.000 --> 00:14:20.040
used this before it looks like it visually represents what's going on a

00:14:17.800 --> 00:14:24.880
little bit differently and it has all cores working on small chunks at a time

00:14:22.959 --> 00:14:30.040
rather than each core working on a tiny tiny tiny little chunk now let's have a

00:14:27.199 --> 00:14:38.560
look at clock speeds are highest boosted core is just over 3 GHz most of them are

00:14:34.000 --> 00:14:41.720
in the 2.6 to 2.8 range though oh wait

00:14:38.560 --> 00:14:44.240
no I lied there's a bunch over here that

00:14:41.720 --> 00:14:48.959
are at 3.1 oh my goodness it's kind of all over the place now I want to look at

00:14:46.320 --> 00:14:54.720
clock speed we've got more course than I was expecting boosting all the way to

00:14:50.880 --> 00:14:57.079
the maximum of 3.1 gahz but most of them

00:14:54.720 --> 00:15:02.880
are somewhere in the 2.8 to

00:14:59.240 --> 00:15:05.839
2.93 GHz range that makes sense remember

00:15:02.880 --> 00:15:11.079
how we talked about these zen4 C cores being more tightly packed than regular

00:15:08.000 --> 00:15:15.000
Zen 4 course that's why our Max boost is

00:15:11.079 --> 00:15:16.839
just 3.1 GHz on this chip but that

00:15:15.000 --> 00:15:23.000
reduced clock speed means that this bergo part shares the same default TDP

00:15:19.720 --> 00:15:26.600
of 360 Watts with the Genoa chip before

00:15:23.000 --> 00:15:28.839
it in spite of the 32 additional course

00:15:26.600 --> 00:15:35.720
plus as served the home found in there testing Bergamo can comfortably run with

00:15:31.480 --> 00:15:37.639
all 128 cores boosting for hours on end

00:15:35.720 --> 00:15:42.279
without neighboring cores interfering with each other maybe we need to do a

00:15:40.040 --> 00:15:48.560
quick pie calculation oh hold on first cinebench is done and we are about four

00:15:45.360 --> 00:15:51.160
times the speed of an apple M1 Ultra

00:15:48.560 --> 00:15:55.959
that is that's a fast chip guys it's not like yeah but whatever it's Apple that's

00:15:53.480 --> 00:16:01.279
a really fast CPU now it's time for more delicious Benchmark using Y cruncher

00:15:58.000 --> 00:16:02.959
will'll be calcul culting pi to oh I

00:16:01.279 --> 00:16:07.199
don't know 250 billion decimal places how much

00:16:05.800 --> 00:16:11.160
round do we have S about right we got a terabyte oh no we don't have a terabyte

00:16:08.800 --> 00:16:17.759
crap we have 768 oh sorry guys it'll have to be a 100 billion decal decimal

00:16:14.160 --> 00:16:20.839
places watch this memory usage

00:16:17.759 --> 00:16:22.759
go they are not turboing as high in this

00:16:20.839 --> 00:16:27.399
workload that tells us that this is a more demanding workload and we could be

00:16:24.639 --> 00:16:31.279
somewhat power limited or VM limited I don't think it's going to be power only

00:16:28.800 --> 00:16:37.160
a little over 300 watts could even be thermals though we managed to hit

00:16:34.360 --> 00:16:41.639
82° on average mind you that's the higher averaged die reading the actual

00:16:39.600 --> 00:16:47.519
ccds themselves where the compute is happening are all in the 55

00:16:45.319 --> 00:16:50.720
range kind of incredible when you consider how much heat is blowing off

00:16:49.199 --> 00:16:54.720
the back of this but that's what having a more spread out heat load will do for

00:16:52.360 --> 00:16:59.079
you wait we can check this we are thermal throttling oh crud we're not

00:16:57.240 --> 00:17:04.039
getting nearly as much performance out of this CPU as we should H is there

00:17:01.680 --> 00:17:07.480
anything we can do about that right now okay hear me out we missed the fins of

00:17:06.480 --> 00:17:12.439
the heat sink that's actually a terrible idea it

00:17:10.600 --> 00:17:17.720
would probably work do we have a spray bottle full of

00:17:16.000 --> 00:17:22.760
alcohol you can make some alcohol interesting

00:17:19.120 --> 00:17:25.240
interesting interesting oh God okay hold

00:17:22.760 --> 00:17:27.880
on hold on let me just this is how fire is made kids no no no no no no no no no

00:17:27.079 --> 00:17:37.880
there's not going to be a fire there's not going to be a fire okay hold on this is the dumbest thing I've ever done it's

00:17:33.760 --> 00:17:40.360
close buddy it's close I need actual

00:17:37.880 --> 00:17:45.720
water though no you can't spray water Don't Spray water can't sounds like a

00:17:42.520 --> 00:17:48.080
challenge to me I've got a shield here

00:17:45.720 --> 00:17:53.080
on the back side so none of the water will end up where it's not supposed to

00:17:50.000 --> 00:17:56.240
be okay let's see if uh let's see if

00:17:53.080 --> 00:17:59.000
that'll help it hey hey look at this CPU

00:17:56.240 --> 00:18:03.799
power consumption 300 WS almost I don't really think it's

00:18:01.720 --> 00:18:06.440
working realistically then we're not going to get a representative reading

00:18:05.120 --> 00:18:10.360
given that we don't have an adequate cooler and this is the only cooler we

00:18:08.400 --> 00:18:15.280
have for this socket so why don't we move on to a load that's not going to

00:18:12.120 --> 00:18:16.679
stress the entire CPU like a video game

00:18:15.280 --> 00:18:21.640
come on you guys you knew we were going to do it go we had to do it

00:18:22.000 --> 00:18:28.960
video oh where's our FP what oh no 50

00:18:26.880 --> 00:18:34.440
frames per second I mean we oh man that's why that's why I

00:18:31.240 --> 00:18:36.559
got shot there are you kidding me

00:18:34.440 --> 00:18:41.679
something I want to clarify is there's nothing architecturally about this CPU

00:18:39.320 --> 00:18:46.720
that makes it bad at running games I've seen it so many times in the comments oh

00:18:44.520 --> 00:18:51.320
is using a server CPU to run games especially when we'll do for example

00:18:48.640 --> 00:18:56.720
older generation Zeon builds as kind of cheap and cheerful gaming rigs but that

00:18:53.280 --> 00:18:59.200
is not the case at all this is the same

00:18:56.720 --> 00:19:04.679
as any other Zen 4 core except that it's running at such a low clock speed that

00:19:02.000 --> 00:19:11.159
it's just not able to keep up with our poor 490 that's

00:19:06.799 --> 00:19:16.720
like wants to go it wants to go but it

00:19:11.159 --> 00:19:21.280
can't go oh crap wow human that guy was

00:19:16.720 --> 00:19:25.520
terrible no offense buddy but wow we're

00:19:21.280 --> 00:19:28.480
using 96 W this this is just not working

00:19:25.520 --> 00:19:32.600
guys I've also got another game to try's see if something a little bit more

00:19:30.159 --> 00:19:38.840
multi-threaded is going to do better now that's more like it over 200 frames per

00:19:36.000 --> 00:19:44.080
second clearly there is something about CS2 that does not like having a slow CPU

00:19:42.080 --> 00:19:50.400
I mean we know it runs way faster with a faster one but I was not expecting it to

00:19:46.440 --> 00:19:52.679
be that bad yeah we're getting 180 FPS

00:19:50.400 --> 00:19:56.520
I'm only at 1080p mind you but if we had a CPU bottleneck we should be quite CPU

00:19:54.960 --> 00:20:00.159
bottleneck regardless of the resolution we're running at I mean this is a 4090

00:19:58.200 --> 00:20:05.200
so that's not going to hold us back CPU usage is at

00:20:01.600 --> 00:20:07.559
0% oh then it goes up to 25 uh then back

00:20:05.200 --> 00:20:11.640
to zero what what what are you even talking about you know what it doesn't

00:20:09.320 --> 00:20:15.360
matter the reality is nothing we run here is a real test of what these chips

00:20:13.559 --> 00:20:20.480
are capable of or what they're designed for and prepackaged benchmarks for cloud

00:20:18.080 --> 00:20:24.799
workloads are few and far between with most customers for a product like this

00:20:23.120 --> 00:20:29.520
either being the kinds of folks who build data Centric capacity then lease

00:20:27.240 --> 00:20:33.600
it to third party and let the customers figure out the rest or the kinds that

00:20:31.320 --> 00:20:38.039
operate at such a large scale that they would expect to receive samples from

00:20:35.600 --> 00:20:41.880
either AMD or their own budgets that they would use to optimize their

00:20:39.400 --> 00:20:47.159
workloads and evaluate the suitability based on real world testing and honestly

00:20:45.400 --> 00:20:53.240
seems like things are going pretty well for AMD on both fronts with their

00:20:49.919 --> 00:20:55.320
massive lead in core counts and PCIe iio

00:20:53.240 --> 00:20:58.799
everyone from Microsoft and meta to Amazon and Google is building up

00:20:56.840 --> 00:21:04.080
infrastructure around bergam Mo and other epic CPUs and with Intel's Sierra

00:21:01.520 --> 00:21:08.440
Forest response using stripped down efficiency cores and being as much as 8

00:21:06.360 --> 00:21:12.159
months away it doesn't look like that's going to be changing in the near future

00:21:10.640 --> 00:21:17.520
so opteron might have ultimately fizzled

00:21:14.559 --> 00:21:22.360
out but epic looks poised to continue making massive gains in the data center

00:21:20.080 --> 00:21:29.640
well at least until the competition from ARM-based competitors gets even stronger

00:21:25.960 --> 00:21:32.559
strong like my segue game to our sponsor

00:21:29.640 --> 00:21:36.080
ODU okay it's 2023 and you're telling me your business doesn't have a website

00:21:34.159 --> 00:21:39.919
whether you're going from town to town Hawking your wares maybe with a

00:21:38.000 --> 00:21:44.279
horsedrawn carriage if you want to improve customer engagement and increase

00:21:42.000 --> 00:21:49.360
conversions you need a website and ODU can help you with that their open source

00:21:46.480 --> 00:21:54.320
platform is easy to use and best of all any single app and its supporting apps

00:21:51.400 --> 00:21:58.240
are 100% free and don't worry if you don't have any coding experience ODU

00:21:56.279 --> 00:22:01.880
keeps it simple with drag and drop elements and an intuitive website

00:21:59.960 --> 00:22:06.080
configurator allowing you to quickly build your site and get back to what's

00:22:03.919 --> 00:22:11.039
important that business that you're running ODU provides unlimited hosting

00:22:08.880 --> 00:22:14.799
support and they even pay for your custom domain name for the first year

00:22:13.320 --> 00:22:18.960
and if you need more than just a basic website ODU is scalable with over 50

00:22:17.400 --> 00:22:22.600
apps available meaning that you only have to install the ones that fit into

00:22:20.760 --> 00:22:26.320
your business needs and they're all fully integrated so give your business

00:22:24.520 --> 00:22:29.880
the companion it needs visit the link down below and start creating a website

00:22:28.080 --> 00:22:33.120
site for free if you guys enjoyed this video especially this little piece of

00:22:31.440 --> 00:22:35.840
History shout out Wolfman mods you can check out his Fallout modding efforts at

00:22:34.679 --> 00:22:40.440
his channel we'll have that link down below and if you're looking for something else to watch why don't you

00:22:38.480 --> 00:22:46.440
check out our coverage of Epic Genoa the full fat non compact version of zen4

00:22:44.279 --> 00:22:51.320
Epic it has a lot more in common with the upcoming thread RI for 7000 CPUs

00:22:49.120 --> 00:22:58.520
that I remember that thing I said before about making its way to the desktop it's

00:22:54.480 --> 00:22:58.520
coming it's happening