WEBVTT

00:00:00.240 --> 00:00:07.200
two terabytes of RAM

00:00:04.000 --> 00:00:09.679
how on earth do you pack two terabytes

00:00:07.200 --> 00:00:14.559
of RAM onto a single system i mean it sounds crazy to say it out loud

00:00:12.400 --> 00:00:20.880
and it is a little crazy i mean unless you're looking at exotic quad or eight

00:00:17.680 --> 00:00:22.880
CPU socket designs even a server grade

00:00:20.880 --> 00:00:28.320
motherboard like this one from Gigabyte typically tops out in the neighborhood

00:00:24.480 --> 00:00:31.119
of 16 memory slots so step one then

00:00:28.320 --> 00:00:36.399
is we are going to need some very special memory a single stick of this

00:00:34.800 --> 00:00:41.440
RAM has more capacity than your entire

00:00:39.280 --> 00:00:46.879
system one of these is 128gb

00:00:44.399 --> 00:00:51.280
of memory and naturally to hit two terabytes as advertised in the video

00:00:48.879 --> 00:00:55.600
title we are going to need a lot of them

00:00:53.440 --> 00:01:02.079
sk hynix is also promoting their new gold s31 SSD every component of the gold

00:00:59.039 --> 00:01:03.840
s31 sata3 SSD was produced built and

00:01:02.079 --> 00:01:07.119
designed by sk hynix to meet their quality and performance standards we're

00:01:05.519 --> 00:01:10.320
going to be using this as our boot drive during our testing and i'm going to have

00:01:08.799 --> 00:01:17.720
a link to where you guys can learn more in the video description

00:01:21.119 --> 00:01:28.159
i've got to ground myself here i'm pretty sure sk hynix isn't sending me more of these if i zap them so get ready

00:01:26.320 --> 00:01:32.320
for a technical deep dive guys traditional registered server dimms

00:01:30.560 --> 00:01:37.680
operate in parallel such that effectively each of the individual

00:01:34.560 --> 00:01:39.680
memory chips on the module is wired

00:01:37.680 --> 00:01:44.720
directly to the memory controller that's built into the CPU so that's where all

00:01:42.479 --> 00:01:48.479
the traces that you see running between your memory slots and your CPU socket

00:01:47.040 --> 00:01:52.720
come into play now there are two ways that you can

00:01:50.479 --> 00:01:58.560
increase the capacity of a memory module you can add more chips by putting them

00:01:55.280 --> 00:02:00.000
on both sides or by double stacking them

00:01:58.560 --> 00:02:06.079
like we see here or you can actually engineer the chips

00:02:02.799 --> 00:02:07.439
themselves with more data areas or

00:02:06.079 --> 00:02:13.040
ranks a dual rank memory module might have

00:02:09.920 --> 00:02:16.000
exactly the same number of visible chips

00:02:13.040 --> 00:02:21.920
soldered onto it but it's effectively like smushing two single ranked modules

00:02:18.720 --> 00:02:24.720
into a single slot and a quadrant module

00:02:21.920 --> 00:02:27.680
is like stuffing four modules into a single slot

00:02:25.920 --> 00:02:31.599
which is pretty cool if you need more capacity but

00:02:29.680 --> 00:02:37.200
it causes a small problem the memory controller on a given CPU has

00:02:34.480 --> 00:02:42.879
a limited number of ranks that it can be wired into directly before performance

00:02:39.680 --> 00:02:45.519
starts to drop off or it reaches a hard

00:02:42.879 --> 00:02:49.519
limit so you might run into cases in the server world where even though a

00:02:47.360 --> 00:02:55.360
motherboard has you know let's say 16 slots you could populate all of them

00:02:52.640 --> 00:02:59.840
with dual rank modules or only half of them with quad rank modules and then

00:02:57.840 --> 00:03:04.000
running at a reduced speed there's not much point in doubling your memory

00:03:01.680 --> 00:03:09.040
density if you cut away half of your expansion slots and some speed right

00:03:06.400 --> 00:03:12.080
like that's classic one step forward two steps back

00:03:10.640 --> 00:03:17.040
so we're getting around that problem today using what's called load reduced

00:03:14.640 --> 00:03:22.000
or lr dimms and there is a lot of engineering packed into these they run

00:03:19.280 --> 00:03:27.280
at a blistering 29 33 megahertz so that is the rated speed of our AMD epic 64

00:03:24.480 --> 00:03:32.560
core processor and they have both a ninth chip in each one of these rows

00:03:30.000 --> 00:03:38.000
for ecc or error correction and an extra memory buffer chip that

00:03:36.080 --> 00:03:43.840
allows the processor's memory controller to operate in serial mode this serial

00:03:40.879 --> 00:03:49.280
operation causes a quad rank dim to load the memory controller like a dual rank

00:03:46.000 --> 00:03:50.239
dim or an 8 rank dim to operate like a

00:03:49.280 --> 00:03:55.040
quad now it comes with a performance penalty

00:03:52.400 --> 00:03:59.680
but if you find any matching places i'm not talking to you siri

00:03:57.360 --> 00:04:02.959
what what even is this what are you talking about

00:04:01.040 --> 00:04:08.400
now it comes with a performance penalty but if your workload requires a ton of

00:04:05.599 --> 00:04:13.720
memory taking a small latency hit is a lot better than not having enough RAM at

00:04:10.720 --> 00:04:13.720
all

00:04:18.400 --> 00:04:23.919
set a good example i love these sockets where you just

00:04:21.519 --> 00:04:28.720
screw the cooler right into the socket just need a boot SSD so all the

00:04:26.880 --> 00:04:33.759
memory volatile or otherwise in our system is actually made by sk hynix in

00:04:31.120 --> 00:04:37.360
korea they're one of only a handful of actual memory manufacturers

00:04:36.080 --> 00:04:42.800
in the world and they've been making ssds for years but it's only recently

00:04:40.560 --> 00:04:46.639
that they branched out of just system builders and enterprise users into

00:04:45.440 --> 00:04:50.639
retail so let's get Windows 10 loaded up on this puppy

00:04:53.680 --> 00:04:59.280
moment of truth time server boards lack a lot of the creature comforts of

00:04:57.120 --> 00:05:04.160
consumer boards so we're just going to short a couple pins turn it on

00:05:02.320 --> 00:05:07.759
like i'm standing here eagerly waiting but i'm not actually expecting it to do

00:05:05.919 --> 00:05:11.199
anything anytime soon every time you boot up a motherboard

00:05:09.520 --> 00:05:14.560
with a new hardware configuration it needs to go through a process called

00:05:12.560 --> 00:05:17.199
memory training and the more RAM you have the longer it takes so this could

00:05:15.919 --> 00:05:20.720
take like 10 minutes to turn on the first time

00:05:20.800 --> 00:05:26.800
it may have taken long enough for a wardrobe change lttstore.com

00:05:24.960 --> 00:05:32.560
but we're up 2 million 97

00:05:29.000 --> 00:05:34.880
152 megabytes of memory running at 29 33

00:05:32.560 --> 00:05:39.759
million transfers per second 64 cores of processor goodness and i

00:05:37.600 --> 00:05:44.400
actually got a cool tip from Gigabyte that apparently if you pop in here and

00:05:42.000 --> 00:05:47.440
ignore all of this warning stuff right here you can actually

00:05:45.600 --> 00:05:53.280
overclock your memory on this platform so it turns out the maximum limit for

00:05:50.479 --> 00:05:57.440
installed memory for Windows 10 pro happens to be

00:05:54.479 --> 00:06:05.199
boom you guessed it exactly two terabytes so this is a bog standard

00:06:01.840 --> 00:06:07.120
Windows 10 install with

00:06:05.199 --> 00:06:11.919
zero percent memory usage

00:06:09.520 --> 00:06:16.560
i could probably even open up chrome and it would still be zero

00:06:14.479 --> 00:06:20.479
percent before we proceed with our entire test though i do plan to find out

00:06:18.800 --> 00:06:24.240
just how many tabs we can handle i want to have a look at what performance looks

00:06:22.160 --> 00:06:28.639
like with our configuration it's worth noting that our 64 core processor

00:06:26.240 --> 00:06:33.360
actually doesn't have smt enabled so it's only running 64 threads it's a bit

00:06:31.680 --> 00:06:37.319
of an idiosyncrasy of this board right now and i haven't spent any time

00:06:35.600 --> 00:06:41.680
figuring out boom 52.44 seconds so we're not looking at

00:06:40.240 --> 00:06:44.880
some kind of you know crippling performance difference or anything like

00:06:43.360 --> 00:06:48.880
that so we got to figure out a good way to do this so brandon hit me with some

00:06:46.880 --> 00:06:55.280
websites youtube all right b h photo video i just got

00:06:51.520 --> 00:06:56.880
some neopets in there you know linkedin

00:06:55.280 --> 00:07:02.880
what are you talking about brandon what are you doing on linkedin

00:06:59.199 --> 00:07:04.639
oh she's sure yeah hey there he is

00:07:02.880 --> 00:07:08.720
nope this is a terrible linkedin profile all right it seems like he's

00:07:06.400 --> 00:07:14.000
seems like he's sticking around new grounds oh i love it and we'll head

00:07:11.440 --> 00:07:18.639
over to the mkbhd store this is my favorite uh 10 million subscriber

00:07:16.319 --> 00:07:22.639
commemorative merch right here chrome is actually using two and a half gigs of

00:07:20.880 --> 00:07:25.919
RAM right now doing functionally nothing

00:07:25.120 --> 00:07:29.520
so it's a hog still it just doesn't make a

00:07:28.560 --> 00:07:36.479
dent it doesn't even register it's flatlined

00:07:32.639 --> 00:07:38.800
so let's do it let's open all 20 tabs in

00:07:36.479 --> 00:07:45.919
a new window yes i'm sure all right we jumped from 5 to 5.8

00:07:43.599 --> 00:07:50.080
now i wanna find out if cycling through them actually increases it so we're

00:07:47.680 --> 00:07:53.599
gonna control tab over through all these tabs and see if it jumps

00:07:56.560 --> 00:08:03.360
it's gonna slow us down quite a bit in terms of how many tabs we can open per

00:08:01.120 --> 00:08:07.280
minute here if we have to do that and it looks like we don't

00:08:05.120 --> 00:08:13.680
hey that's great news so now this just becomes an exercise in

00:08:10.160 --> 00:08:15.280
how fast can i click this is super dumb

00:08:13.680 --> 00:08:19.599
i want a piece of paper you know i'm going to start tallying how

00:08:16.960 --> 00:08:25.599
many tabs i'm opening i need paper update for you guys

00:08:21.199 --> 00:08:32.000
at 200 chrome tabs we are now at 10 gigs

00:08:25.599 --> 00:08:36.399
of RAM and 1 usage 600 tabs 700 tabs 900

00:08:32.000 --> 00:08:38.000
tabs 1 000 tabs

00:08:36.399 --> 00:08:44.159
5 this is interesting neopets seems to be

00:08:41.120 --> 00:08:47.120
our heaviest website first you take my

00:08:44.159 --> 00:08:52.240
youth then you take my CPU cycles we are up to 69 CPU usage well i think we're

00:08:50.560 --> 00:08:56.120
gonna run at a CPU before we run out of memory here guys we are over one stick

00:08:54.560 --> 00:09:01.200
of memory use now 132 gigs chrome at least admits that

00:08:59.120 --> 00:09:08.720
it's using over 100 gigs of RAM now power usage very high 5 000 tabs here we

00:09:05.120 --> 00:09:09.920
go boys rent hey we're at 10 RAM usage

00:09:08.720 --> 00:09:14.800
now so that's sick

00:09:12.000 --> 00:09:20.480
but what's interesting is that in spite of us having resources available to us

00:09:18.240 --> 00:09:24.240
the system is getting slower and slower and slower to the point where even when

00:09:22.000 --> 00:09:29.120
this ad managed to load in i couldn't help but notice it was running at a

00:09:26.080 --> 00:09:30.880
super crazy low resolution look at this

00:09:29.120 --> 00:09:35.440
here here's a perfect example it just froze while it was playing back that's

00:09:32.640 --> 00:09:40.959
what it looks like opening a hundred now when we already have 5000 open in the

00:09:37.440 --> 00:09:43.519
background was like opening up the first

00:09:40.959 --> 00:09:48.800
500 when we did it now this is interesting i was going to rearrange the

00:09:46.000 --> 00:09:53.760
tabs to shoot the thumbnail and we got a spike in CPU usage and i'm not sure if

00:09:51.760 --> 00:09:57.440
memory actually changed but check this out a bunch of these tabs

00:09:55.600 --> 00:10:02.080
that were already open before are reloading now so it seems like

00:09:59.360 --> 00:10:06.240
interacting with the window actually gets it to refresh but that

00:10:04.560 --> 00:10:10.080
doesn't change our RAM usage and since that's what we're after i guess that's

00:10:07.600 --> 00:10:13.200
still okay uh-oh oh no

00:10:11.279 --> 00:10:16.800
we might have hit our limit brandon

00:10:14.480 --> 00:10:23.440
brandon i'm rolling we might have hit our limit brendan

00:10:20.160 --> 00:10:23.440
but i want to get the thumbnail

00:10:24.560 --> 00:10:29.600
if i have to open them all again to get the damn thumbnail it's gonna suck

00:10:28.320 --> 00:10:35.200
six thousand we're at the point now we're doing

00:10:32.720 --> 00:10:39.279
almost anything in chrome on the system i'm trying to combine a tab i

00:10:37.440 --> 00:10:45.120
accidentally dragged out of a browser window back into it and it just

00:10:42.880 --> 00:10:48.079
it's not responsive enough to do it but what oh hey

00:10:46.800 --> 00:10:52.399
it did it okay so we got that

00:10:50.640 --> 00:10:56.720
i mean gimp's managing to open up so that's cool

00:10:53.680 --> 00:10:59.120
we are just shy of 200 gigs of memory

00:10:56.720 --> 00:11:02.720
usage now and that's just from rearranging all the

00:11:00.880 --> 00:11:09.440
tabs we were at closer to like 185 weren't we this is so weird check this

00:11:05.040 --> 00:11:09.440
out this up here says amazon

00:11:09.600 --> 00:11:15.839
but mkbhd is also selected and this is

00:11:12.640 --> 00:11:15.839
an apple website

00:11:17.760 --> 00:11:22.480
so strictly speaking we may not be at

00:11:20.880 --> 00:11:27.279
the limit but from a practical standpoint

00:11:25.120 --> 00:11:32.160
i think we've reached the limit oh no i think i just did the wavy thing

00:11:29.120 --> 00:11:32.160
where everything minimizes

00:11:34.160 --> 00:11:40.880
the system is completely unusable at this point

00:11:38.000 --> 00:11:47.279
look at them all go a right click three four five six seven 25 20 there it

00:11:46.000 --> 00:11:50.480
is just shy of 30 seconds just to right

00:11:49.600 --> 00:11:55.200
click so we only managed to use about a tenth of

00:11:53.920 --> 00:11:58.720
our RAM half of our CPU

00:11:56.959 --> 00:12:04.880
but we seem to have reached architectural limits of the software

00:12:01.519 --> 00:12:08.480
itself whether it's chrome or Windows

00:12:04.880 --> 00:12:11.680
and 6000 tabs is well beyond what is

00:12:08.480 --> 00:12:13.120
actually usable in google chrome i hope

00:12:11.680 --> 00:12:17.760
you guys enjoyed coming along with us on the ride massive shout out to sk hynix

00:12:15.360 --> 00:12:21.360
for sponsoring this video sending over two terabytes of memory even though we

00:12:19.440 --> 00:12:26.079
didn't manage to use it all this time and of course providing their

00:12:23.440 --> 00:12:30.720
gold s31 SSD for us to boot off of it's available in 250 gig 500 gig and one

00:12:28.720 --> 00:12:34.480
terabyte capacities it comes with a five year warranty and if you're looking for

00:12:32.399 --> 00:12:37.920
a high performance say SSD you guys can check it out it is at the link in the

00:12:36.320 --> 00:12:42.720
video description so thanks for watching guys hope you had as much fun as we did

00:12:40.720 --> 00:12:46.560
with this insanity and we will see you in the next video if

00:12:44.800 --> 00:12:49.680
you enjoy more server type content like this we actually built a crazy nas a

00:12:48.399 --> 00:12:52.480
little while ago you can check out that video down below