WEBVTT

00:00:05.680 --> 00:00:09.840
they're the same picture except they're not

00:00:08.960 --> 00:00:14.639
this is a boring old u.2 drive you can find

00:00:12.320 --> 00:00:19.520
these puppies with up to a four lane pci express gen 4 interface

00:00:16.480 --> 00:00:20.560
and up to about 8 gigabytes per second

00:00:19.520 --> 00:00:29.039
speed which is okay i guess but it's not nearly as cool as this

00:00:26.000 --> 00:00:32.719
u.3 doesn't increase speeds

00:00:29.039 --> 00:00:36.559
at all and in fact it could even be

00:00:32.719 --> 00:00:38.480
much slower but it could also be

00:00:36.559 --> 00:00:42.160
the same speed which

00:00:39.600 --> 00:00:46.239
doesn't really sound that great does it until i tell you that it also allows

00:00:44.640 --> 00:00:51.920
cross-compatibility with sas and even SATA drives in exactly

00:00:50.480 --> 00:00:58.160
the same slot what that's right my friends this connector

00:00:55.120 --> 00:01:00.879
here is basically like putting a usb

00:00:58.160 --> 00:01:06.640
drive in a firewire port and we've got both a drive from kyoccia who sponsored

00:01:03.359 --> 00:01:09.760
this video and this server over here

00:01:06.640 --> 00:01:13.400
from super micro and we are going to be

00:01:09.760 --> 00:01:13.400
testing it out

00:01:20.000 --> 00:01:25.840
u.3 is super new so while the drives are

00:01:23.200 --> 00:01:30.960
readily available hardware to actually plug them into is still pretty hard to

00:01:28.479 --> 00:01:35.840
find our server for example only supports u.2 fortunately kyoccia

00:01:34.159 --> 00:01:39.600
provided us with everything we're going to need starting with

00:01:38.640 --> 00:01:44.000
this now in the old days controller cards

00:01:41.840 --> 00:01:48.720
like this one usually had built-in specialty processors on board to perform

00:01:46.399 --> 00:01:53.600
the parity calculations that protected the attached raid array from data loss

00:01:51.360 --> 00:02:00.000
over time though hardware raid cards have given way to hbas or host bus

00:01:56.479 --> 00:02:02.719
adapters that simply convert your pci

00:02:00.000 --> 00:02:07.840
express slot into dumb storage ports leaning on the

00:02:05.360 --> 00:02:10.959
general purpose CPU to do the heavy lifting

00:02:08.879 --> 00:02:15.360
this kind of software raid is more flexible more cost effective and it's

00:02:13.840 --> 00:02:19.920
easier for administrators to troubleshoot and repair and these are

00:02:17.920 --> 00:02:25.680
actually some of the big driving forces behind the u.3 standard so this broadcom

00:02:23.840 --> 00:02:31.200
9516i is what's called a tri-mode storage

00:02:28.000 --> 00:02:34.640
adapter it uses a pci express gen 4x8

00:02:31.200 --> 00:02:38.720
interface and can address up to 1024

00:02:34.640 --> 00:02:42.720
SATA or sas drives using expanders or up

00:02:38.720 --> 00:02:46.080
to 32 NVMe drives now let's have a look

00:02:42.720 --> 00:02:49.280
at the broadcom lrond yes that's right

00:02:46.080 --> 00:02:51.200
my friends it's a custom external u.3

00:02:49.280 --> 00:02:55.040
testing enclosure that's designed for research and development of new drives

00:02:53.200 --> 00:02:59.120
and adapter cards to make sure that they interface with servers correctly in

00:02:57.040 --> 00:03:04.560
other words this isn't something that you can just go out and buy

00:03:01.680 --> 00:03:09.360
normally the way it would work is a u.3 backplane like the one that's built into

00:03:06.800 --> 00:03:13.519
this enclosure would just be directly in the server behind the bays at the front

00:03:11.519 --> 00:03:18.400
and you would plug right into them but as of right now we haven't found any

00:03:15.519 --> 00:03:22.319
servers with native u.3 support at least that we can get our hands on hp

00:03:20.400 --> 00:03:26.879
enterprise is one of the only brands that's shipping u.3 technology currently

00:03:24.720 --> 00:03:31.200
though lenovo has also expressed their support for it so here we go we just

00:03:28.959 --> 00:03:36.400
install our try mode card into our caddy here and

00:03:33.840 --> 00:03:39.680
plonk that into our server oh

00:03:37.599 --> 00:03:43.519
contact believe it or not we haven't even turned

00:03:41.040 --> 00:03:43.519
it on yet

00:03:44.799 --> 00:03:49.370
ah there it is here we go

00:03:48.480 --> 00:03:56.640
you're ready now one little trick is normally you

00:03:54.000 --> 00:04:00.799
would run these cables internally to the back plane at the front of the device

00:03:58.560 --> 00:04:08.560
obviously right well that's not a try mode u.3 backplane

00:04:04.640 --> 00:04:08.560
so we're just going to kind of

00:04:11.840 --> 00:04:16.959
yeah good it's good cooling gotta have

00:04:15.040 --> 00:04:19.759
air holes on the side okay here we go

00:04:18.560 --> 00:04:22.720
very funny what am i putin

00:04:23.520 --> 00:04:29.919
i'm gonna be next level impressed if this manages like hot swap functionality

00:04:28.560 --> 00:04:36.400
now you might have noticed that even though we've only got an 8x card

00:04:32.960 --> 00:04:38.160
we've got four 4x capable cables coming

00:04:36.400 --> 00:04:42.240
out of here that's because that bandwidth can be shared it's in much the

00:04:39.919 --> 00:04:45.040
same way that even if you did plug in a thousand

00:04:43.440 --> 00:04:48.320
sas drives obviously if you were actually hitting

00:04:46.880 --> 00:04:51.680
them all at once they would have to share some of that bandwidth

00:04:50.560 --> 00:04:57.919
what do you think is this just gonna like magically

00:04:55.120 --> 00:05:01.600
hot swap pickup wait probably not because we don't have

00:04:59.680 --> 00:05:07.440
a drive in it yet one moment please this just feels so wrong

00:05:05.120 --> 00:05:12.960
SATA port u.3 connector okay here we go

00:05:12.960 --> 00:05:20.880
just like that put it online initialize

00:05:18.080 --> 00:05:26.080
blah blah blah ouch

00:05:22.479 --> 00:05:29.919
60 megabytes a second reads

00:05:26.080 --> 00:05:33.680
not exactly impressive but of course the

00:05:29.919 --> 00:05:35.120
performance of u.3 was never the point

00:05:33.680 --> 00:05:39.039
there's nothing you can do with an interface to make a

00:05:36.880 --> 00:05:43.759
two and a half inch hard drive suddenly magically fast

00:05:40.880 --> 00:05:49.199
the point is that we can do this this is a sas SSD

00:05:46.880 --> 00:05:53.680
and theoretically i'm gonna pop that right in there hot swap

00:05:51.520 --> 00:05:56.960
and it's going to just like work wait for it

00:05:56.960 --> 00:06:02.499
there it is

00:06:02.720 --> 00:06:08.400
we can run a quick performance test here there it is you can see it's a lot

00:06:05.759 --> 00:06:13.440
faster of course it's an SSD it's not a mechanical hard drive but the point here

00:06:11.199 --> 00:06:18.400
again is not the performance it's to demonstrate how just because you've got

00:06:16.000 --> 00:06:22.960
one physical connector doesn't mean that you can't use different protocols over

00:06:20.960 --> 00:06:26.800
it and that's really this is a much more appropriate analogy

00:06:25.199 --> 00:06:30.960
for what we're doing today than the whole usb firewire thing because those

00:06:29.440 --> 00:06:37.360
are completely different physical connectors SATA and sas already used the

00:06:34.560 --> 00:06:41.600
same connector just a different protocol so that's what we've looked at so far

00:06:39.840 --> 00:06:46.960
but now ah uh this one

00:06:43.440 --> 00:06:48.400
now it's time to put in a gen4 pci

00:06:46.960 --> 00:06:54.400
express SSD using again the same u.3 connector this

00:06:51.360 --> 00:06:57.199
is a cm6 from kyoxia which was the first

00:06:54.400 --> 00:07:03.520
available u.3 drive on the market and it's rated at up to

00:06:59.080 --> 00:07:06.319
6900 megabytes per second nice

00:07:03.520 --> 00:07:11.440
just like our merch is nice like the CPU pillow lttstore.com now

00:07:09.199 --> 00:07:14.639
you probably noticed i just shoved that in there

00:07:12.319 --> 00:07:18.960
is hot swap gonna work i actually don't know because i've had some pretty bad

00:07:16.400 --> 00:07:24.160
experiences hot swapping pci express devices oh oh ouch

00:07:21.919 --> 00:07:28.319
but that's supposed to be one of the benefits as the technology has matured

00:07:26.960 --> 00:07:33.199
is we're supposed to be able to take any kind of drive we want chuck it in there

00:07:30.720 --> 00:07:37.680
hot swap cold swap let's see if it's in here there it is

00:07:35.440 --> 00:07:42.319
online it and boom we've got our e drive

00:07:39.759 --> 00:07:46.400
i'm expecting this to be a lot faster and it is now

00:07:46.479 --> 00:07:54.319
wait a minute you might say that's not 6 900 megabytes per second

00:07:52.800 --> 00:07:58.960
that's not nice but we're not actually reaching the

00:07:56.960 --> 00:08:06.000
drive full speed because of two bottlenecks in our setup one this system

00:08:02.080 --> 00:08:08.560
has two epic 7702 processors pretty cool

00:08:06.000 --> 00:08:13.520
but although each of them has 64 cores and 128 threads they are single core

00:08:11.520 --> 00:08:17.120
performance isn't particularly impressive because of their low clock

00:08:15.199 --> 00:08:21.759
speed and with this setup on Windows server 2019 we're not taking advantage

00:08:19.759 --> 00:08:28.479
of the drive's full potential but we can still try out u.3 hotspot oh

00:08:26.319 --> 00:08:32.479
interesting so okay we're taking it one step further

00:08:30.560 --> 00:08:37.440
with the hotting and the swapping apparently

00:08:33.599 --> 00:08:37.440
i'm just gonna pull out a SATA drive

00:08:37.919 --> 00:08:42.479
i'm gonna pull out an NVMe drive

00:08:42.800 --> 00:08:45.039
okay

00:08:50.320 --> 00:08:57.200
and theoretically they're just gonna come back my script says react to the

00:08:55.279 --> 00:09:00.160
hot swap just working we've got ooh

00:08:58.480 --> 00:09:03.519
we've got e no the SATA drive is missing what if i

00:09:02.320 --> 00:09:10.959
rep seriously boom all three of them are there so

00:09:07.040 --> 00:09:13.760
we've got SATA ooh and e

00:09:10.959 --> 00:09:18.160
okay then what does all this mean for me the average consumer for the time being

00:09:16.720 --> 00:09:23.120
probably not much i don't expect that u.3 is going to be

00:09:20.240 --> 00:09:27.120
sweeping in to replace the popular m.2 gumstick form factor in your home gaming

00:09:24.959 --> 00:09:31.680
pc anytime soon but in the data center it offers a

00:09:29.440 --> 00:09:36.880
couple of clear benefits one of which is visible right on the face of it see

00:09:34.240 --> 00:09:41.600
these cooling holes i call them speed holes because adequate cooling allows

00:09:39.279 --> 00:09:46.880
these drives to perform their best even when they're under heavy load 24 7 like

00:09:44.399 --> 00:09:51.760
they would be in an enterprise or data center setting the other thing that the

00:09:49.200 --> 00:09:56.560
larger form factor does is it allows the drives to have more capacity because

00:09:53.839 --> 00:10:01.440
they can physically solder more nand dyes to the thing than can fit on a

00:09:59.040 --> 00:10:05.760
simple little gum stick so for the data center these are going to be huge

00:10:03.360 --> 00:10:09.839
not just because they have a single connector that natively supports

00:10:07.440 --> 00:10:12.880
multiple protocols that's not anything new we already showed that with SATA and

00:10:12.000 --> 00:10:18.720
sas the big deal is that it allows a single

00:10:16.000 --> 00:10:24.480
server with a single type of bay in the front to serve all kinds of different

00:10:21.680 --> 00:10:30.000
roles so manufacturers instead of having to have different skus for like a slower

00:10:27.200 --> 00:10:34.560
bulk storage box and then a faster all NVMe one are going to be able to have

00:10:32.160 --> 00:10:38.959
just a single sku simplifying their product development and simplifying

00:10:36.640 --> 00:10:43.120
their product stack that data center administrators can just deploy however

00:10:41.040 --> 00:10:48.480
they want so i want this one to be all NVMe i want this one to be all sas i

00:10:46.000 --> 00:10:53.920
want this one to be you know NVMe accelerant over here and then sas mass

00:10:51.040 --> 00:10:59.120
storage over there it's totally up to the admin and that

00:10:56.079 --> 00:11:00.800
is super super cool another fringe

00:10:59.120 --> 00:11:04.720
benefit actually that we heard from one of the techs that's working on this is

00:11:02.800 --> 00:11:08.959
that it makes uh trying out different hardware configurations and

00:11:06.320 --> 00:11:14.800
troubleshooting way simpler because you can just use one machine for all of your

00:11:12.240 --> 00:11:18.720
test benches instead of having to like move giant servers around as you're

00:11:17.120 --> 00:11:22.640
testing out different drives and configs so that's uh that's another thing

00:11:21.279 --> 00:11:26.480
thanks to you guys for watching thanks to kyoccia for sponsoring this one you

00:11:24.640 --> 00:11:31.120
guys can get more details about their cm6 drives and the rest of their

00:11:28.560 --> 00:11:35.279
technology at the link down below if you guys are interested in the backstory

00:11:32.880 --> 00:11:39.279
behind my nightmare experience hot swapping pci express devices you can

00:11:37.680 --> 00:11:45.640
check out the video that we have linked in the description as well this was a

00:11:42.399 --> 00:11:45.640
much smoother