WEBVTT

00:00:05.600 --> 00:00:11.599
This video is brought to you by the Corsair Vengeance K70 and K95. These

00:00:09.840 --> 00:00:15.120
fully mechanical keyboards are designed for performance gaming. Visit

00:00:13.200 --> 00:00:19.039
Corsair.com/benancegaming to learn more. Welcome to my unbagging

00:00:17.119 --> 00:00:22.560
of something that I personally think is really important and really interesting,

00:00:20.800 --> 00:00:25.600
but you might disagree, but I mean, come on. At this point, you clicked on the

00:00:24.000 --> 00:00:33.040
video. You might as well watch it, right? This is the creatively named

00:00:28.400 --> 00:00:35.200
Seagate Desktop SSHD 2000 Gigabyte.

00:00:33.040 --> 00:00:40.320
Really like whoever names their products uh they get an award for being very

00:00:38.160 --> 00:00:44.960
practical. Um so what it is is it is their first desktop hybrid drive. So it

00:00:42.719 --> 00:00:50.320
contains in spite of its normal 3 and 12 in form factor and normal SATA 36 Gbit

00:00:47.840 --> 00:00:54.000
per second interface a regular mechanical 3 and 12 in drive. So, it's

00:00:52.160 --> 00:00:57.680
available in 1 TB or two terabyte. Although there a little birdie told me

00:00:55.760 --> 00:01:00.960
there might be a a higher capacity one later. Although saying that there might

00:00:59.359 --> 00:01:04.159
be a higher capacity hard drive later is about like saying the sun might rise.

00:01:02.800 --> 00:01:08.799
Like they really are about the same probability because if the sun stopped rising then all the hard drives would

00:01:06.880 --> 00:01:14.799
probably go away anyway. Um so it contains a mechanical hard drive as well

00:01:11.600 --> 00:01:16.880
as an SSD inside that completely doesn't

00:01:14.799 --> 00:01:20.560
need to be configured at all. So, the 8 gig SSD, and that's seems pretty small,

00:01:19.119 --> 00:01:25.280
but more on that in a moment, dynamically finds the data that you use

00:01:22.640 --> 00:01:29.680
most often and caches it in there for much, much faster reads. Now, there's a

00:01:28.159 --> 00:01:34.240
little bit of a writing strategy as well, but not nearly to the same extent

00:01:31.759 --> 00:01:37.680
as it uses the SSD for reads, which is really important, particularly for

00:01:35.920 --> 00:01:41.920
things like your operating system. So, if you're getting used to devices like

00:01:40.159 --> 00:01:46.000
smartphones and tablets and even ultrabooks to a lesser extent that run

00:01:43.920 --> 00:01:48.640
strictly off of flash, you're probably getting used to a level of

00:01:47.119 --> 00:01:52.799
responsiveness that just can't be achieved through pure mechanical. That's

00:01:51.040 --> 00:01:55.920
where the SSD comes in. So even though it's quite small, you're able to cache

00:01:54.640 --> 00:01:59.840
the things that are going to make your system feel really responsive, but

00:01:57.840 --> 00:02:04.479
you're able to have that large capacity backup for things like large games that

00:02:02.079 --> 00:02:08.000
you want to install or large programs like, I don't know, you know, Adobe

00:02:05.920 --> 00:02:11.200
Suite or or things like that. And it really does give sort of the best of

00:02:09.360 --> 00:02:15.440
both worlds. In addition to performance, you're also going to potentially

00:02:13.680 --> 00:02:18.080
make the device last longer. So there's a few different ways of looking at this.

00:02:16.720 --> 00:02:22.080
Number one is you're adding more points of failure when you have SSD as well as

00:02:20.319 --> 00:02:25.599
mechanical. Number two, though, is that you're making them inherently last

00:02:23.599 --> 00:02:30.400
longer because SSDs don't like being written to. Eventually, they will die.

00:02:27.920 --> 00:02:33.200
Um, but what happens is because you're not always writing things directly to

00:02:31.680 --> 00:02:36.879
the SSD, you're actually writing to the hard drive, the SSD only gets written to

00:02:35.519 --> 00:02:41.280
when it's something that you use very, very frequently. And SSDs don't get worn

00:02:39.360 --> 00:02:45.280
out by reading from them. Okay. Then there's the mechanical drive that gets

00:02:43.280 --> 00:02:48.640
worn out about equally from reading and writing. So, you have to write it to it

00:02:46.879 --> 00:02:51.920
regardless. But what if you could read all of your most frequently used data

00:02:50.160 --> 00:02:55.599
from the SSD, which doesn't really wear out? See where I'm going with this? So,

00:02:53.920 --> 00:02:59.200
you could potentially get a longevity benefit as well. Now, this

00:02:57.440 --> 00:03:02.959
implementation is not the beall and endall of a hybrid solution. So, if you

00:03:01.120 --> 00:03:08.080
have two separate drives, you can use Intel SRT to use an SSD to cache a hard

00:03:05.680 --> 00:03:12.480
drive completely separately. And there are actually drives being manufactured

00:03:09.920 --> 00:03:16.159
with a single interface that have two separately addressable drives inside

00:03:14.159 --> 00:03:20.959
them. This is one of the benefits of say a 36 GB per second, right? Because

00:03:18.800 --> 00:03:23.519
you've got tons of bandwidth there as long as you're not talking about

00:03:22.000 --> 00:03:27.200
extremely high performance like enthusiast grade SSDs. There are other

00:03:25.840 --> 00:03:32.000
implementations as well. I mean, Microsoft's working on ways to have the

00:03:29.280 --> 00:03:38.000
OS handle some of the SSD caching itself. And Intel, um, Seagate and

00:03:35.840 --> 00:03:43.200
Western Digital worked on an extension to the SATA 3 IO that is going to allow

00:03:41.120 --> 00:03:47.440
the drives themselves, which really do know more about what's going on inside

00:03:45.280 --> 00:03:51.040
them than the OS necessarily does, to start providing hints to the OS about

00:03:49.120 --> 00:03:55.440
what to cache and when and where. So, the future is extremely exciting. And I

00:03:53.440 --> 00:04:01.760
believe that as much as I use solid state only in my desktop machines, I do

00:03:58.720 --> 00:04:03.599
use mechanical for mass storage over the

00:04:01.760 --> 00:04:07.840
network. So as much as I believe in solid state and love it, I do believe

00:04:05.360 --> 00:04:13.120
that a hybrid is going to be the future, at least for the near to midterm. So

00:04:11.200 --> 00:04:20.400
guys, do check this out. It's the Seagate Desktop SSHD.

00:04:16.479 --> 00:04:21.759
The most interesting name ever. Um, and

00:04:20.400 --> 00:04:26.080
don't forget to subscribe to Lines Tech Tips for unboxings, reviews, and other computer videos. Leave a like if you

00:04:24.720 --> 00:04:29.680
like the video, leave a dislike if you dislike the video, and leave a comment

00:04:27.840 --> 00:04:32.680
if you think my nose is too big for my face.
