WEBVTT

00:00:00.080 --> 00:00:06.319
we're used to getting revisions of computer standards fairly regularly

00:00:03.760 --> 00:00:10.719
think about how many versions of usb ddr and pci express we've been through but

00:00:08.639 --> 00:00:16.240
we haven't had to put much thought into NVMe so far as there's only been one

00:00:13.440 --> 00:00:21.520
major version of it until now as the NVMe 2.0 standard has just been released

00:00:19.439 --> 00:00:25.760
in case you're out of loop NVMe or non-volatile memory express is the

00:00:23.600 --> 00:00:30.240
protocol that pci express connected storage drives use because it's much

00:00:28.160 --> 00:00:33.520
faster than the older SATA standard it's enabled those gaudy four figure

00:00:32.320 --> 00:00:38.239
throughput numbers you see on manufacturer spec sheets for m.2 drives

00:00:36.079 --> 00:00:42.719
and the NVMe 2.0 specification is bringing some new features to the table

00:00:40.399 --> 00:00:47.440
so let's dive right in one of the major improvements is for something called

00:00:44.640 --> 00:00:51.200
zoned namespaces and that might sound like some kind of forward thinking

00:00:49.039 --> 00:00:55.920
therapy collective but it's actually a system designed to address some of the

00:00:53.199 --> 00:01:00.000
biggest issues with ssds you see even though ssds are a lot faster than

00:00:58.079 --> 00:01:04.640
old-school spinning hard drives there's a significant amount of inefficiency

00:01:02.559 --> 00:01:09.680
under the hood because the cells in an SSD can only be written to so many times

00:01:07.119 --> 00:01:14.640
before they wear out for good the SSD's internal logic has to move data around

00:01:12.000 --> 00:01:18.880
in a process called wear leveling to make sure certain cells don't exhaust

00:01:16.400 --> 00:01:24.240
their lifespans more quickly than others additionally ssds can't directly

00:01:21.759 --> 00:01:29.119
overwrite cells instead cells have to have their data erased first

00:01:27.040 --> 00:01:34.240
and this has to be done in groups of cells so any data in that group that the

00:01:31.520 --> 00:01:39.280
system needs to preserve must be copied to an empty area ssds reserve a certain

00:01:37.200 --> 00:01:43.439
amount of space called over provisioning to support these data operations meaning

00:01:41.759 --> 00:01:50.159
a significant amount of storage is inaccessible to the user NVMe 2.0 zoned

00:01:47.680 --> 00:01:55.920
namespaces help alleviate this situation by allowing programs to reserve specific

00:01:52.720 --> 00:01:58.000
physical areas on the SSD and write data

00:01:55.920 --> 00:02:02.479
for that program sequentially without zone name spaces the SSD itself would be

00:02:00.479 --> 00:02:06.640
in charge of what data goes where and this often results in a specific

00:02:04.320 --> 00:02:11.280
program's data being scattered all over the drive meaning that any changes to

00:02:09.119 --> 00:02:16.560
that data could require lots of those read copy delete actions that use a

00:02:14.080 --> 00:02:21.440
large amount of over provisioned space but with zoned namespaces a smaller

00:02:18.959 --> 00:02:27.360
physical footprint per program means the SSD won't have to over provision as much

00:02:24.160 --> 00:02:29.520
space nor do so many reads and writes

00:02:27.360 --> 00:02:33.920
meaning effectively larger drives with better endurance for the same cost and

00:02:32.160 --> 00:02:38.879
programs could also see a performance boost from zone name spaces as ssds read

00:02:36.480 --> 00:02:43.280
and write sequential data faster than they do random data so not only is this

00:02:41.440 --> 00:02:47.120
good for consumers like you and me but larger organizations should see an even

00:02:45.360 --> 00:02:52.400
greater benefit than us since when you're running lots of ssds in parallel

00:02:49.760 --> 00:02:57.599
such as inside a gigantic server farm having that much wasted space and

00:02:55.120 --> 00:03:02.480
latency can have a significant negative impact not to mention the direct cost of

00:03:00.080 --> 00:03:06.560
having to replace drives that wear out the second significant benefit of NVMe

00:03:04.720 --> 00:03:10.400
2.0 that we're going to discuss today is it's surprising support for mechanical

00:03:09.040 --> 00:03:15.680
hard drives but why would it support mechanical hard

00:03:12.800 --> 00:03:21.120
drives i mean even higher end drives can't come anywhere close to using the

00:03:17.599 --> 00:03:23.360
full bandwidth of plain old SATA so

00:03:21.120 --> 00:03:27.360
what gives it turns out that recent advances in hard drive manufacturing

00:03:25.120 --> 00:03:31.840
have allowed drives to read data off the platters more quickly partly due to

00:03:29.440 --> 00:03:36.080
improvements in the actuators that move the drive parts around and partly due to

00:03:34.400 --> 00:03:40.080
fitting more data on the platters themselves through techniques like heat

00:03:38.560 --> 00:03:45.040
assisted magnetic recording which you can learn about up here

00:03:42.560 --> 00:03:48.879
hammer time this means that some hard drives that are just starting to hit the

00:03:46.400 --> 00:03:53.760
market can get sustained transfer rates above 500 megabytes per second

00:03:51.280 --> 00:03:58.159
sequentially which is comparable to SATA based ssds

00:03:55.519 --> 00:04:02.560
NVMe 2.0 will provide enough bandwidth to ensure newer hard drives can max out

00:04:00.159 --> 00:04:06.560
their potential especially important in larger settings that use lots of hard

00:04:04.400 --> 00:04:11.200
drives for mass storage they can share data among themselves quickly of course

00:04:08.799 --> 00:04:15.920
because the NVMe 2.0 spec was released recently it'll be a while before we see

00:04:13.920 --> 00:04:20.959
products that support it but hopefully the result will be larger cheaper drives

00:04:18.799 --> 00:04:25.600
for your home pc and quicker more reliable access to cloud services i just

00:04:23.840 --> 00:04:29.600
wouldn't expect disney to slash the price of your streaming subscription

00:04:27.520 --> 00:04:33.919
with the money they're saving on drives world doesn't tend to work like that

00:04:31.840 --> 00:04:38.320
big thank you to today's sponsor private internet access vpn they help you mask

00:04:36.400 --> 00:04:43.360
your true ip address and they encrypt your traffic with reliable service and

00:04:40.400 --> 00:04:46.800
no bandwidth caps pia has configurable encryption and an internet kill switch

00:04:45.360 --> 00:04:52.000
which keeps you in control of your connection combine it with private browsing and make websites think you're

00:04:50.000 --> 00:04:56.320
in a different country plus you can connect up to 10 devices at once with

00:04:53.840 --> 00:05:00.880
clients for Windows mac Android iOS and Linux pia has also recently launched its

00:04:58.800 --> 00:05:05.360
new dedicated ip option which offers an even smoother internet experience while

00:05:02.960 --> 00:05:10.639
maintaining your privacy and security with over 25 000 servers in 78 countries

00:05:08.160 --> 00:05:14.080
what are you waiting for try pia risk free for 30 days at the link below so

00:05:12.960 --> 00:05:18.240
thanks for watching guys if you like this video hit like hit subscribe and

00:05:16.560 --> 00:05:22.880
hit us up in the comment section with your suggestions for topics that we

00:05:19.600 --> 00:05:22.880
should cover in the future