WEBVTT

00:00:14.920 --> 00:00:20.960
so okay this thing is really weird you

00:00:18.800 --> 00:00:25.119
guys like it looks like a regular old oh there we go m.2

00:00:24.000 --> 00:00:31.279
SSD but not only can you glue one of these

00:00:28.560 --> 00:00:38.879
to one of these but you can actually have it show up as a single drive of up

00:00:34.480 --> 00:00:41.760
to 32 terabytes and they also claim that

00:00:38.879 --> 00:00:47.680
built into this thing they've got slc flash you guys remember slc one cell

00:00:45.120 --> 00:00:54.719
equals one bit super fast super reliable and super expensive but

00:00:51.200 --> 00:00:56.800
at a price of just 330 dollars just what

00:00:54.719 --> 00:01:00.800
kind of scam are these guys trying to pull here i don't know but i know our

00:00:59.199 --> 00:01:05.119
sponsor ridge wallet isn't pulling any scams ridge wallet wants to redefine the

00:01:03.039 --> 00:01:08.720
wallet with its compact frame and rfid blocking plates check out how they can

00:01:07.040 --> 00:01:13.840
keep your wallet bulge down and use offer code Linus to save 10

00:01:10.640 --> 00:01:13.840
and get free worldwide shipping

00:01:21.200 --> 00:01:26.400
when i say SSD and modis probably isn't

00:01:24.320 --> 00:01:30.720
the first word to pop into your mind but chances are that you have heard of them

00:01:28.240 --> 00:01:35.680
before even if it was indirectly their fuse drive tiered storage software was

00:01:33.360 --> 00:01:41.600
actually licensed by AMD as the first version of their store my raid feature

00:01:38.000 --> 00:01:43.600
for ryzen and threadripper and this as

00:01:41.600 --> 00:01:51.040
far as i can tell is their first consumer hardware offering an SSD that's

00:01:47.680 --> 00:01:53.680
also called fusedrive they say it's two

00:01:51.040 --> 00:02:00.880
ssds in one and runs with artificial intelligence that gives it endurance as

00:01:55.680 --> 00:02:00.880
good as a samsung 970 pro which

00:02:00.960 --> 00:02:07.280
you smell that kind of smells like grade a marketing to

00:02:05.119 --> 00:02:10.959
me i mean it's challenging enough to put one SSD in a package to size let alone

00:02:10.160 --> 00:02:16.239
two and we can clearly see from the pcb

00:02:13.599 --> 00:02:22.879
layout and the markings on the dies that this is just a regular vanilla qlc SSD

00:02:20.000 --> 00:02:27.920
with a single controller on it except maybe it's not the big reason why adding

00:02:26.080 --> 00:02:33.120
layers causes endurance to drop is because of the voltages required to

00:02:30.080 --> 00:02:36.400
write to each layer but what most people

00:02:33.120 --> 00:02:39.200
don't realize is that multi-level nand

00:02:36.400 --> 00:02:44.239
can be used in a single level mode where only a single layer of each cell is

00:02:41.680 --> 00:02:50.000
actually used at a time now it cuts the capacity of

00:02:45.840 --> 00:02:52.480
qlc to one quarter but it also offers

00:02:50.000 --> 00:02:57.599
nearly the same speed and nearly the same endurance of native slc this

00:02:55.519 --> 00:03:03.280
concept is nothing new though and large vendors like Intel or samsung have

00:03:00.160 --> 00:03:04.959
actually been using this slc mode to

00:03:03.280 --> 00:03:10.720
cache their drives and improve performance for years now but here's the

00:03:07.519 --> 00:03:13.840
new idea most ssds that use slc mode

00:03:10.720 --> 00:03:16.239
caching use a dynamically sized cache

00:03:13.840 --> 00:03:23.040
rather than dedicating a chunk of the SSD for it and non-tech reports that

00:03:19.040 --> 00:03:27.120
Intel 660p for example starts out with

00:03:23.040 --> 00:03:30.080
76 gigabytes of slc cache but then that

00:03:27.120 --> 00:03:35.519
can go as low as just six gigs as the drive fills up that means that it will

00:03:32.239 --> 00:03:37.680
sacrifice over time both the performance

00:03:35.519 --> 00:03:42.879
and endurance that it was supposed to gain from the slc cache so

00:03:40.720 --> 00:03:47.519
back to in modis's marketing claims then they're taking a different approach by

00:03:44.560 --> 00:03:55.519
creating a permanently segmented one and a half terabyte qlcssd with a separately

00:03:51.040 --> 00:03:57.439
addressable 128 gig slc portion i didn't

00:03:55.519 --> 00:04:00.439
put a graphics card in here one moment please

00:04:04.640 --> 00:04:11.519
man i love how unhappy the d drive is you know what i'm saying it's so upset

00:04:10.080 --> 00:04:15.760
hey the performance looks all right though it's rated for 34 megabytes per

00:04:13.920 --> 00:04:20.479
second reads and it's just shy of that and rated for 3 000

00:04:18.400 --> 00:04:25.440
megabytes per second writes which is fine just fine for a qlc SSD wait no

00:04:23.759 --> 00:04:30.000
that's really good for qlc now those numbers are much better than what you'd

00:04:27.199 --> 00:04:34.639
expect writing to qlc flash that is the range that i would expect as long as the

00:04:31.919 --> 00:04:39.919
slc cache is working correctly because that is way better than what we would

00:04:36.639 --> 00:04:43.120
see writing to in particular qlc flash

00:04:39.919 --> 00:04:45.680
in qlc mode compared to our pci express

00:04:43.120 --> 00:04:49.199
gen 4 tlc boot drive though these numbers

00:04:46.639 --> 00:04:53.440
don't look that impressive even with enmodis's slc caching

00:04:51.680 --> 00:04:57.919
what they also have up their sleeve though is the ability to quickly and

00:04:55.280 --> 00:05:02.479
easily extend the SSD volume with a hard drive so let's see how that looks you

00:05:00.800 --> 00:05:09.039
can see this illustrated when we compare to our pci express gen 4 tlc boot drive

00:05:06.400 --> 00:05:13.600
read speeds thanks to the wider bus are way better on that one but ride speeds

00:05:11.840 --> 00:05:18.320
because we're not taking advantage of an slc cache actually

00:05:15.840 --> 00:05:21.330
kind of suck by comparison theoretically this is as simple as plugging in a hard

00:05:20.080 --> 00:05:23.360
drive

00:05:23.360 --> 00:05:30.960
we then fire up in modis's fusion x software and we're going to make a

00:05:28.080 --> 00:05:37.759
non-bootable fuse drive so our in modus SSD is our fast drive

00:05:35.199 --> 00:05:40.160
and our seagate hard drive is our slow i mean i

00:05:38.720 --> 00:05:44.720
i guess we could do it the other way around but that would be very stupid oh

00:05:42.320 --> 00:05:47.840
hey here it goes oh wow you can actually un-tier it when you're done if you don't

00:05:46.560 --> 00:05:54.160
like it anymore for whatever reason that's cool truthfully i kind of

00:05:49.759 --> 00:05:56.720
expected the 128 gig slc drive to appear

00:05:54.160 --> 00:06:01.360
separately in device manager but it doesn't it's just

00:05:58.639 --> 00:06:06.080
permanently allocated to accelerate your one and a half terabyte SSD so in a way

00:06:03.840 --> 00:06:09.759
this is not dissimilar to when people used to manually over provision the

00:06:08.160 --> 00:06:12.639
flash in their drives for more consistent performance way back in the

00:06:11.440 --> 00:06:16.560
day before trim and garbage collection had matured

00:06:14.720 --> 00:06:22.160
to the point that they have now oh it's done drive 3

00:06:19.280 --> 00:06:25.199
is made up of drives two and one one plus two is three

00:06:25.360 --> 00:06:33.919
oh and so our fuse drive all two tiers of it are

00:06:30.800 --> 00:06:38.560
totally invisible to me now and it just

00:06:33.919 --> 00:06:40.160
shows up as a 12.3 terabyte hard drive

00:06:38.560 --> 00:06:43.919
so we've got all the capacity of both but they're combined let's just like i

00:06:42.240 --> 00:06:46.800
don't know let's just throw some let's throw some footage onto it or something

00:06:45.919 --> 00:06:51.360
okay the SSD caching is definitely working

00:06:49.280 --> 00:06:54.800
what i want is to actually hit the hard drive i want to see this go down to like

00:06:52.800 --> 00:06:58.880
200 megabytes a second Anthony says i won't be able to do it but i i see that

00:06:56.880 --> 00:07:02.560
as a challenge while this is running is actually a good time to bring up that

00:07:00.160 --> 00:07:06.319
you can run a configuration like this as your boot drive so you can actually run

00:07:05.039 --> 00:07:11.680
Windows off of this which as we've talked about numerous times in the past

00:07:08.560 --> 00:07:14.880
is an ideal use case for this type of

00:07:11.680 --> 00:07:16.639
caching or tiering solution because your

00:07:14.880 --> 00:07:21.919
operating system tends to hit the same files many many

00:07:19.440 --> 00:07:26.560
many times and then most of it can sit in cold or warm storage only to be

00:07:24.319 --> 00:07:31.919
accessed infrequently and that's exactly how this works

00:07:29.120 --> 00:07:34.639
i'm just gonna keep doing this yeah we're still well over two gigs a

00:07:33.680 --> 00:07:39.280
second you know what i was probably expecting

00:07:37.120 --> 00:07:44.240
to be able to break through it because most of the caching solutions that i've

00:07:41.199 --> 00:07:45.360
used before use much much smaller ssds

00:07:44.240 --> 00:07:50.639
but i mean even though it's qlc flash it's

00:07:48.479 --> 00:07:55.520
much faster than a hard drive so being able to write two i mean a terabyte and

00:07:53.120 --> 00:08:00.080
a half of SSD means you would i mean it would come up but you would

00:07:56.960 --> 00:08:02.560
basically never actually see that hard

00:08:00.080 --> 00:08:06.560
drive like speed maybe the first time you load up you know call of duty if you

00:08:04.639 --> 00:08:09.199
haven't played it in a year you know you would have to actually pull

00:08:07.919 --> 00:08:13.599
the whole thing from hard drive but then it should promote that data into the SSD

00:08:11.599 --> 00:08:18.400
so the next time you fire it up it's quick one of the dangers however of

00:08:16.000 --> 00:08:24.720
using a nand based storage device like an SSD as a cache is that a right cache

00:08:21.919 --> 00:08:27.680
well by its very nature gets written to far more frequently than a drive that

00:08:26.240 --> 00:08:32.080
you're just using normally because you write to it once when you write the data

00:08:30.000 --> 00:08:36.240
to the combined drive and then if that data gets demoted it gets replaced with

00:08:34.000 --> 00:08:40.479
something else and then if it gets promoted back into the cache you write

00:08:38.000 --> 00:08:42.719
that same data again that can be really problematic

00:08:41.680 --> 00:08:46.880
but and modis says that with their

00:08:45.600 --> 00:08:53.720
gold endurance they managed to

00:08:49.760 --> 00:08:57.440
somehow dramatically outperform the mere

00:08:53.720 --> 00:09:00.480
600 program erase cycles that their qlc

00:08:57.440 --> 00:09:02.320
nand is rated for i mean how can they

00:09:00.480 --> 00:09:06.959
claim with a straight face that their drive is good for something like three

00:09:04.800 --> 00:09:11.760
times the endurance that samsung advertises for their shiny new 980 pro

00:09:10.720 --> 00:09:17.519
i mean we we looked at it this is a fairly bog

00:09:14.320 --> 00:09:20.080
standard fizen controller qlc SSD well

00:09:17.519 --> 00:09:25.440
it turns out this data is kind of a your mileage may vary situation and modis

00:09:22.800 --> 00:09:31.839
says that hot data that is frequently accessed spends a lot more of its time

00:09:27.920 --> 00:09:34.560
in that slc portion than on the warm qlc

00:09:31.839 --> 00:09:38.560
layer so unlike traditional slc caching where storage from the whole drive is

00:09:36.560 --> 00:09:42.640
used for in-flight rights and then they just flush out the cache when it's idle

00:09:40.880 --> 00:09:47.680
and modis is using a dedicated eight-channel nand chip and their

00:09:44.720 --> 00:09:52.080
tiering mechanism activates on right so writes are immediately done on slc

00:09:50.399 --> 00:09:56.320
then they're only moved out when they haven't been modified in a while that

00:09:53.920 --> 00:10:00.959
actually helps prevent wear on the qlc layers now for something like our

00:09:57.760 --> 00:10:03.519
blackmagic cameras where we put m.2 ssds

00:10:00.959 --> 00:10:07.519
into usb enclosures and then can write as much as the entire drive in a single

00:10:05.600 --> 00:10:12.480
session there'd be next to no benefit from this approach but for a desktop

00:10:09.920 --> 00:10:16.959
user who's not likely to routinely write hundreds of gigabytes of data or when

00:10:15.120 --> 00:10:21.839
they do it might be a program or game that they're also going to be you know

00:10:18.640 --> 00:10:23.600
playing and using frequently for a bit

00:10:21.839 --> 00:10:27.360
starting to make a lot of sense and that's exactly who modis says they're

00:10:25.200 --> 00:10:30.720
marketing these drives for for the time being they're only available directly

00:10:29.360 --> 00:10:34.399
from in modis but they're hoping to partner with system integrators in the future

00:10:33.680 --> 00:10:38.320
so bottom line it's always a balancing act

00:10:36.800 --> 00:10:41.440
you've got your price you got your performance and you've got your

00:10:39.920 --> 00:10:46.720
endurance pick too but and modis thinks they've

00:10:44.000 --> 00:10:52.000
got that sweet spot that comes closest to picking all three and they actually

00:10:49.680 --> 00:10:55.920
even put RGB on it even though we never did turn that on you do of course give

00:10:53.760 --> 00:11:00.160
up a little of each of those things to get this kind of balance though so what

00:10:57.839 --> 00:11:02.959
do you guys think is it worth it one thing i know is worth it is subscribing

00:11:01.600 --> 00:11:07.120
on Floatplane for that sweet behind-the-scenes content madison did a

00:11:04.959 --> 00:11:12.000
an office tour that was very her style for sure i'm sorry i did make

00:11:09.440 --> 00:11:14.399
you look bad i didn't mean to and it's also worth checking out our

00:11:13.440 --> 00:11:20.000
sponsor ting thanks to ting mobile for sponsoring today's video they've got new

00:11:18.320 --> 00:11:24.079
rates that make it easier than ever to see how much you can save by switching

00:11:21.680 --> 00:11:29.360
to ting unlimited talk and text is just 10 and data plans start at 15 with

00:11:27.040 --> 00:11:33.200
unlimited data for 45 dollars a month and if you liked their previous pay for

00:11:31.040 --> 00:11:37.519
what you use plans they're still there they're just called ting flex plans and

00:11:35.120 --> 00:11:41.360
they charge just five dollars a gig data can also be shared if you have a family

00:11:39.120 --> 00:11:45.120
plan so you can connect more phones to save more and you'll get the same

00:11:43.040 --> 00:11:48.720
nationwide coverage in the us and award-winning customer service that you

00:11:46.800 --> 00:11:53.200
remember pretty much any phone will work with ting so check them out at

00:11:50.440 --> 00:11:56.720
Linus.ting.com and you can get a 25 credit towards your account

00:11:54.959 --> 00:12:01.519
if you guys enjoyed this video maybe check out one of our previous videos

00:11:58.560 --> 00:12:08.240
exploring the concept of SSD or optane caching on slower spinning rust

00:12:05.760 --> 00:12:13.000
really is cool stuff enterprise storage concepts in your gaming pc