WEBVTT

00:00:00.080 --> 00:00:06.720
it's not exactly unusual for us to dabble in the extreme the insane the top

00:00:05.359 --> 00:00:13.200
of the line so when i say this might be one of the

00:00:09.760 --> 00:00:14.240
fastest servers in the entire flippin

00:00:13.200 --> 00:00:21.199
world i mean it you guys might remember when we took a look at liquids honey badger a

00:00:18.960 --> 00:00:28.400
pci express card capable of housing eight NVMe ssds with speeds in the 28 to

00:00:24.560 --> 00:00:31.439
30 Gigabyte per second range well

00:00:28.400 --> 00:00:34.559
this box dubbed the badger den sent over

00:00:31.439 --> 00:00:36.719
by our friends at liquid has five

00:00:34.559 --> 00:00:42.800
honey badgers in it and can supposedly maintain sequential read speeds in

00:00:38.320 --> 00:00:45.280
excess of 100 gigabytes per second that

00:00:42.800 --> 00:00:48.320
is bites not bits holy

00:00:47.120 --> 00:00:52.000
and today i get to put my grubby little fingers

00:00:50.559 --> 00:00:54.960
all over it and you're gonna help me

00:00:56.559 --> 00:01:02.559
just like pulseways gonna help us sponsor this video pulseway is a

00:01:01.280 --> 00:01:06.240
real-time remote monitoring and management software solution that allows

00:01:04.479 --> 00:01:09.840
you to control systems and support your users from anywhere it helps you fix

00:01:08.320 --> 00:01:13.840
problems even when you're on the go by sending commands from any mobile device

00:01:11.760 --> 00:01:17.159
with their app go check them out at the link below

00:01:26.560 --> 00:01:32.000
what do you mean you can't even see anything yet i can see the honey badgers

00:01:30.720 --> 00:01:35.600
look at them one two three four five so that's a

00:01:34.159 --> 00:01:41.360
total of 40 m.2 drives

00:01:38.320 --> 00:01:43.280
40. so to put those numbers i threw at

00:01:41.360 --> 00:01:47.840
you in the intro in perspective you could copy your average 4k blu-ray which

00:01:45.840 --> 00:01:53.920
is somewhere between 50 and 100 gigabytes in a second or even less it

00:01:51.360 --> 00:01:59.840
would happen so fast there wouldn't even be a Windows transfer dialog box it's

00:01:56.479 --> 00:02:01.119
just moved bam just like that

00:01:59.840 --> 00:02:05.360
now Windows isn't actually a great example

00:02:03.200 --> 00:02:09.280
of how this performance would behave in the real life because i guarantee you

00:02:07.520 --> 00:02:14.080
there is no way we will get anywhere near that figure on Windows regardless

00:02:11.599 --> 00:02:17.440
of what the physical hardware can do but we're still going to try our best

00:02:15.920 --> 00:02:22.480
i have Windows installed on here right yeah yeah it's the dumbest thing ever but let's do it

00:02:20.239 --> 00:02:25.920
it's not even a Windows server Windows 10 pro it's not like it's

00:02:24.480 --> 00:02:30.720
different look at these fans they got their own

00:02:28.560 --> 00:02:38.160
built-in shots these are finger cutters ladies and gentlemen

00:02:32.360 --> 00:02:41.440
3.3 amps these are 40 watt fans

00:02:38.160 --> 00:02:45.440
40 watts wait what is that right what is

00:02:41.440 --> 00:02:48.840
it 12 volts 3.3 amps yeah at full speed

00:02:45.440 --> 00:02:51.200
one two three four five six this is

00:02:48.840 --> 00:02:55.280
250 watts of fans

00:02:53.360 --> 00:03:00.640
oh the whole thing comes out look at that that's my look they're hot

00:02:58.319 --> 00:03:05.280
you got to be kidding me their hot swap here

00:03:02.000 --> 00:03:07.760
and their hot swap there like what oh oh

00:03:05.280 --> 00:03:13.920
i simply couldn't be arsed to replace just one fan at a time in this server so

00:03:11.440 --> 00:03:18.400
i'll just you know what screw it we'll just toss it and we'll get a whole new

00:03:15.920 --> 00:03:22.920
bank of fans yeah there we go that'll take care of it now we got 250 watts of

00:03:20.959 --> 00:03:29.040
cooling let's go boys holy mackerel this has just got a plain

00:03:26.560 --> 00:03:32.879
face plate got that liquid silk screening on there this is pretty

00:03:31.200 --> 00:03:37.360
typical having like modules in the front of these things so if we didn't have all

00:03:35.360 --> 00:03:41.200
the pci express slots full and we could actually allocate more lanes to the

00:03:39.040 --> 00:03:45.440
front bays we could put another couple of these in here and have a total of 24

00:03:43.200 --> 00:03:52.159
drives in the front of this thing and unlike our last attempt to put 24 nvmes

00:03:49.120 --> 00:03:54.560
into a 2u server we've got

00:03:52.159 --> 00:04:00.280
dual cpus this time so hopefully we got enough pci express and

00:03:56.959 --> 00:04:00.280
enough CPU

00:04:02.560 --> 00:04:08.560
yeah okay all right oh it's only a little broken there

00:04:07.120 --> 00:04:12.640
just throw the whole thing away i'll get too mad to build me a new one no i

00:04:10.239 --> 00:04:16.239
brokey look at this

00:04:14.799 --> 00:04:23.520
what you're looking at here ladies and gentlemen is 128

00:04:19.919 --> 00:04:27.280
CPU cores 256 threads so these are each

00:04:23.520 --> 00:04:31.600
64 core epic processors and

00:04:27.280 --> 00:04:35.199
32 sticks of 32 gigs of memory running

00:04:31.600 --> 00:04:37.120
at 3 200 megahertz that is no mean feat

00:04:35.199 --> 00:04:42.960
when you consider that both cpus are fully populated that is

00:04:40.479 --> 00:04:47.040
fast memory for a server but as we learned before it makes a big difference

00:04:45.360 --> 00:04:53.440
when you're trying to do something like this so wait what do you what even is that

00:04:50.240 --> 00:04:56.320
64 128 256

00:04:53.440 --> 00:05:02.639
holy sh that's a terabyte of RAM i'ma install me

00:04:58.720 --> 00:05:04.720
some call of duty on RAM why not i could

00:05:02.639 --> 00:05:10.720
so two of our honey badgers are fully kitted out with eight by four terabytes

00:05:07.520 --> 00:05:13.120
so that's 32 terabytes of storage on a

00:05:10.720 --> 00:05:17.840
single card the other three just have some poop mix of whatever ssds liquid

00:05:16.160 --> 00:05:21.680
sent over so we are going to end up leaving some performance on the table

00:05:19.280 --> 00:05:26.000
today but we'll talk about how we plan to rectify that in the future i should

00:05:24.479 --> 00:05:32.960
pull out a badger so if you guys aren't familiar with what a honey badger looks like you can see it what the devil

00:05:29.680 --> 00:05:36.320
connector is this this is so cool

00:05:32.960 --> 00:05:39.039
so that's going to be a pci express 16x

00:05:36.320 --> 00:05:44.160
interface i guess isn't it two yeah it's two of them no one's a blank on this one

00:05:42.240 --> 00:05:49.120
i think because there's only one slot on this uh daughter board but i think it

00:05:46.560 --> 00:05:54.880
probably uses the same connector as the other ones new the other ones definitely

00:05:52.400 --> 00:06:00.960
use different connectors oh my goodness this thing is so cool this is a liquid

00:05:57.919 --> 00:06:03.520
honey badger it's got a pci express 16x

00:06:00.960 --> 00:06:07.759
gen 4 interface on the bottom and then a

00:06:04.240 --> 00:06:10.560
very expensive pci express switch so

00:06:07.759 --> 00:06:15.280
that it can use those 16 lanes to address eight

00:06:12.240 --> 00:06:18.639
forex NVMe drives that are installed uh

00:06:15.280 --> 00:06:19.680
you can kind of see them ah yes

00:06:18.639 --> 00:06:24.720
here here here and well

00:06:22.880 --> 00:06:28.400
basically under this heatsink and you might be asking yourselves why would

00:06:26.560 --> 00:06:33.360
they do it in such an expensive manner when you can get cards like this that'll

00:06:30.479 --> 00:06:39.440
take four m.2s for a fraction of the price and the reasons for this are

00:06:36.000 --> 00:06:42.000
twofold number one because well

00:06:39.440 --> 00:06:46.400
twice as many drives per slot hey who's going to say no to that it allowed us to

00:06:44.160 --> 00:06:51.919
effectively double the capacity of this server without having to add well more

00:06:48.960 --> 00:06:56.479
servers so that's good and number two a big part of liquid's jam aside from just

00:06:54.319 --> 00:07:00.880
sending us cool toys to play with is what they call composable infrastructure

00:06:58.960 --> 00:07:07.120
so instead of having servers that have all the CPU GPU and storage in one place

00:07:05.039 --> 00:07:11.039
you'll have entire boxes that are just dedicated to one thing so if this was

00:07:09.199 --> 00:07:16.080
one of our storage boxes then these resources could be allocated dynamically

00:07:13.440 --> 00:07:21.840
through software to this server over here or that application or that

00:07:18.720 --> 00:07:24.240
workload all on the fly and all at full

00:07:21.840 --> 00:07:28.080
speed as if that server was built physically using the hardware here but

00:07:26.400 --> 00:07:32.000
it's actually somewhere else in the data center pretty cool right finally how do we

00:07:30.639 --> 00:07:40.080
power this thing look at that that's it that's 1400 flipping watts of

00:07:36.960 --> 00:07:42.319
power and like a gum stick

00:07:40.080 --> 00:07:45.440
wow a gum work here to kick ass and chew

00:07:44.319 --> 00:07:51.199
bubble gum this is awful gum so it's not even pins

00:07:47.919 --> 00:07:52.639
anymore it's like slabs of contacts

00:07:51.199 --> 00:07:56.319
these are 12 volt only which is interesting so that means like those 12

00:07:54.720 --> 00:08:02.240
volt only power supplies that i showed off that are coming to desktops for improved efficiency the server world

00:08:00.160 --> 00:08:06.479
already beat us there they always get the cool stuff in the enterprise first

00:08:04.720 --> 00:08:11.680
i'm waiting for my composable gaming rigs in my house so it's all on a rack

00:08:08.879 --> 00:08:15.120
and i can just be like okay boy you don't need you know all the powerful GPU

00:08:13.599 --> 00:08:19.520
i'll take that i'm playing among us right now you can have more GPU later

00:08:17.440 --> 00:08:21.680
for your minecrafts or whatever all right let's put this thing back

00:08:20.479 --> 00:08:27.120
together and fire it up are you ready click the button yeah i'm ready to click the button look it's even got lights on

00:08:24.160 --> 00:08:32.240
the power supply as well okay three two one

00:08:28.560 --> 00:08:34.800
i want to hear 250 watts of cooling fans

00:08:32.240 --> 00:08:38.880
i did actually set the fans to the lowest noise level okay

00:08:37.279 --> 00:08:42.719
oh hello here's that's not bad these are the high

00:08:40.880 --> 00:08:47.839
performance fans too this is an upgrade oh yeah all right

00:08:45.200 --> 00:08:47.839
oh there we go

00:08:49.519 --> 00:08:54.959
it's not so bad that's the quietest oh that's not bad at

00:08:54.080 --> 00:08:57.680
all where's the lid

00:09:02.080 --> 00:09:09.550
oh that's not too bad yeah it's not terrible well we'll have

00:09:06.080 --> 00:09:11.440
to cinebench it right oh 100

00:09:11.440 --> 00:09:15.600
see you later oh my gosh

00:09:14.560 --> 00:09:21.440
15 16

00:09:17.920 --> 00:09:23.120
18 seconds ladies and gentlemen

00:09:21.440 --> 00:09:27.519
like what what's the score 49 944

00:09:27.760 --> 00:09:33.680
now you guys might look at that and go well gee that's uh doesn't seem that

00:09:31.440 --> 00:09:38.399
great because a 32 core threadripper can do over half of that and that's only 32

00:09:36.000 --> 00:09:44.959
instead of 128 cores but you got to understand guys this is

00:09:41.120 --> 00:09:47.279
64 cores on a single CPU so you're going

00:09:44.959 --> 00:09:50.800
to have some limitations in terms of the clock speeds you can run them at so

00:09:49.440 --> 00:09:56.880
on that note why don't we see what this thing can do there's a couple options we could either

00:09:53.839 --> 00:09:58.240
do storage spaces yeah cause right now

00:09:56.880 --> 00:10:01.920
all the disks are individual oh my goodness

00:10:01.040 --> 00:10:06.800
there's there's 40 what 42 there's 42 discs in

00:10:04.720 --> 00:10:13.279
here to see how this goes we're going to create a gigantic striped volume across

00:10:10.480 --> 00:10:18.480
16 4 terabyte drives Windows doesn't even manage to get past the first hurdle

00:10:15.360 --> 00:10:19.600
which is combine the disk

00:10:18.480 --> 00:10:26.079
hey there we go so this is just 16 four

00:10:22.000 --> 00:10:28.160
terabyte drives yeah yeah 59 terabytes

00:10:26.079 --> 00:10:32.079
all right crystal disk mark here we go let's pull up our task manager let's see

00:10:29.760 --> 00:10:35.040
how hard we're gonna hit this CPU settings

00:10:33.680 --> 00:10:40.640
so do uh threads do 32 threads 32qs 32 threads

00:10:38.560 --> 00:10:45.040
that's it well two per drop i have so many threads though i'm giving it 32

00:10:42.959 --> 00:10:48.640
threads for everything uh

00:10:46.880 --> 00:10:52.079
sure yo this isn't even all the drives but

00:10:55.200 --> 00:11:02.160
all right holy sh all right Windows

00:10:58.839 --> 00:11:03.440
touche you touched me you touched what

00:11:02.160 --> 00:11:08.880
that's what it means oh okay all right it's touched it's a fencing

00:11:06.399 --> 00:11:16.399
thing oh we can see iops too oh oh that's pretty gross that's abysmal

00:11:12.720 --> 00:11:19.200
yeah so lots of gigabytes per second but

00:11:16.399 --> 00:11:24.320
our iops are actually terrible which means that there's

00:11:21.120 --> 00:11:26.880
there's definitely you know bottlenecks

00:11:24.320 --> 00:11:30.240
i think it's time for us to go to Linux you ready you're ready i'll see you in

00:11:28.959 --> 00:11:34.560
10 minutes from this thing right yeah it takes a while to reboot

00:11:32.000 --> 00:11:39.040
now we've got ubuntu server fired up and this is the part where things get a

00:11:36.240 --> 00:11:42.560
little less visually interesting but i promise they're interesting

00:11:40.720 --> 00:11:48.720
okay here's something visual let's just fire up age top hey look at that we got

00:11:45.600 --> 00:11:50.640
we got too many CPU cores to fit on the

00:11:48.720 --> 00:11:55.200
screen hey

00:11:52.720 --> 00:11:59.360
all right Jake uh this is this is your time to your time to shine i'm just

00:11:57.200 --> 00:12:03.680
gonna i'm gonna get a lysol wipe here so we pre-made a few scripts with liquid we

00:12:01.440 --> 00:12:07.040
have sequential read sequential right 4k random 4k read are you ready for me to

00:12:06.160 --> 00:12:12.240
do it yeah i'm waiting i want to see big numbers big numbers that's all i like i

00:12:10.639 --> 00:12:18.000
just like big numbers even if they don't mean anything no i want big numbers that

00:12:15.440 --> 00:12:22.639
mean that my dick is really big you know okay well i can't help you with that so

00:12:20.000 --> 00:12:25.360
that's the write speed all right so 57

00:12:24.320 --> 00:12:31.519
dang one blu-ray per second this is how my blue rays go that's a lot

00:12:29.680 --> 00:12:39.839
of blue rays bro now now now when i have five blu-rays here we go

00:12:35.760 --> 00:12:42.720
here we go here we go 91 gibby bites

00:12:39.839 --> 00:12:46.399
98 gimme bites what

00:12:44.160 --> 00:12:50.560
is crazy town you guys of course

00:12:47.600 --> 00:12:55.360
while these numbers are very impressive they are not necessarily indicative of

00:12:53.519 --> 00:12:59.519
real world performance if we were to set up some sort of software raid

00:12:57.519 --> 00:13:05.360
configuration on these drives that's because these tests are set up to run

00:13:01.440 --> 00:13:08.639
the i o for each NVMe drive on the CPU

00:13:05.360 --> 00:13:10.720
that that NVMe drive is physically

00:13:08.639 --> 00:13:14.800
actually connected to in the real world

00:13:12.240 --> 00:13:19.360
very few applications are pneuma aware meaning that they don't really pay

00:13:16.160 --> 00:13:21.279
attention to which cores or cpus the

00:13:19.360 --> 00:13:26.079
processing is occurring on so in those cases it's very possible that the CPU

00:13:23.920 --> 00:13:31.839
selected to run a given i o operation for a specific NVMe device may not be

00:13:29.360 --> 00:13:37.120
the one that is directly connected to that NVMe drive so if that happens the

00:13:34.959 --> 00:13:42.720
transfer has to go across the infinity fabric that connects the two cpus which

00:13:39.839 --> 00:13:49.839
can significantly impact performance now we could remedy this by virtualizing new

00:13:46.079 --> 00:13:51.519
new one x server into two vms and only

00:13:49.839 --> 00:13:55.680
passing through the drives that correspond to a CPU but then that would

00:13:53.680 --> 00:13:59.440
leave us with two shares for our poor editors to keep track of and a lot of

00:13:57.279 --> 00:14:03.199
added complexity especially given that in this configuration we are still

00:14:01.440 --> 00:14:07.360
expecting numbers somewhere in the range of 20 to 30 gigabytes per second which

00:14:06.399 --> 00:14:12.560
is way more than our 100 gigabit per second

00:14:10.240 --> 00:14:16.240
networking did i even mention that we have a new 100 gigabit per second

00:14:14.720 --> 00:14:20.720
network switch coming we're going to hook all that up we're going to have all the editors running 25 gig make sure

00:14:19.440 --> 00:14:24.079
you're subscribed so you don't miss that so anyway it's already way more than we

00:14:23.279 --> 00:14:29.199
could possibly take advantage of

00:14:27.279 --> 00:14:33.600
just like i'm going to take advantage of your attention watching this video to

00:14:31.600 --> 00:14:37.680
tell you all about pulse way sorry i needed a second to get pulse wave fired

00:14:35.519 --> 00:14:42.639
up here check it out got our one terabyte of memory i'm covering up our

00:14:39.600 --> 00:14:45.120
external ip here got our zero percent

00:14:42.639 --> 00:14:48.480
CPU usage uh here i'm going to try running a sequential read test and see

00:14:46.720 --> 00:14:52.959
if that jumps up a little bit hey there's the CPU working a little bit

00:14:50.399 --> 00:14:56.959
there pulseway allows you to monitor your servers in real time gives you

00:14:54.880 --> 00:15:00.399
remote desktop functionality you can check system resources logged in users

00:14:58.959 --> 00:15:04.959
network performance you can manage Windows updates and so much more and the

00:15:03.120 --> 00:15:10.720
best part is you can do it on the go from your Android or iOS device you can

00:15:07.920 --> 00:15:14.639
even create deploy and automate custom scripts so you can automate your it

00:15:12.399 --> 00:15:18.800
tasks like deployments patching and security backups and more and their

00:15:17.440 --> 00:15:21.760
endpoint protection allows you to install pulseway antivirus across

00:15:20.560 --> 00:15:26.720
systems and ensure they're fully protected at all times so try it for

00:15:23.839 --> 00:15:30.320
free at pulseway.com or through the link in the video description let's show some

00:15:28.800 --> 00:15:34.880
other interesting stuff that you can do so you can see your storage you can get

00:15:32.800 --> 00:15:39.279
notifications and alerts like if the editors use up all the storage and we

00:15:37.519 --> 00:15:42.560
can set a threshold like 90 it'll ping me or Jake on our phones be

00:15:41.040 --> 00:15:46.079
like hey can you tell those guys to get rid of that stuff run automation scripts

00:15:44.560 --> 00:15:50.399
you can see all the running processes actually we had an issue recently with

00:15:48.560 --> 00:15:54.720
old wanik where the CPU was pinned at 100 because of some application gone

00:15:52.639 --> 00:15:58.240
haywire and that's exactly the kind of thing that pulseway is specifically

00:15:56.320 --> 00:16:02.720
designed to help prevent so it'll tell you proactively when something is

00:16:00.320 --> 00:16:07.040
sucking up all your CPU cycles so if you guys enjoyed this video maybe

00:16:04.959 --> 00:16:11.279
check out the previous video on the deployment of pneumonic which this

00:16:09.600 --> 00:16:16.079
ultimately is probably going to replace so i christened this one new new onik

00:16:13.839 --> 00:16:20.160
and mnemonic is just dead because those Intel drives it turns out are just

00:16:18.160 --> 00:16:23.600
shoddy garbage and they won't rma them for us so

00:16:21.680 --> 00:16:29.360
yeah no i don't i'm not going to call it wanik3 this is

00:16:26.079 --> 00:16:29.360
new new wanik

00:16:29.440 --> 00:16:36.079
look at that new new wanting all right see you later new pneumonic

00:16:34.000 --> 00:16:38.800
should we game on it in a future video do you guys want us to put a graphics

00:16:37.120 --> 00:16:42.199
card in here yeah no yeah