1
00:00:00,160 --> 00:00:05,920
In my hand is 16 terabytes of mechanical

2
00:00:03,600 --> 00:00:12,240
storage. And the crazy part is that's not even cutting edge. WD just announced

3
00:00:08,720 --> 00:00:15,200
18 and 20 terbte hard drives. Both of

4
00:00:12,240 --> 00:00:24,080
which get absolutely wrecked. Buy this.

5
00:00:18,400 --> 00:00:28,000
This is the 100 terabyte aptly named Exa

6
00:00:24,080 --> 00:00:32,079
Drive from Nimbus Data. I have been

7
00:00:28,000 --> 00:00:36,399
waiting literally months to get my hands

8
00:00:32,079 --> 00:00:39,520
on the highest capacity SSD on the

9
00:00:36,399 --> 00:00:43,760
planet. Welcome to a very exciting

10
00:00:39,520 --> 00:00:47,640
installment of Holy.

11
00:00:43,760 --> 00:00:47,640
It's worth $40,000.

12
00:00:48,239 --> 00:00:55,120
But before that, gotcha. Segue time. Ridge Wallet wants to redefine the

13
00:00:52,879 --> 00:00:59,039
wallet with its compact frame and RFID blocking plates. Check out how they can

14
00:00:57,120 --> 00:01:06,039
help keep your wallet bulged down and use our offer code Linus to save 10% and

15
00:01:02,000 --> 00:01:06,039
get free worldwide shipping.

16
00:01:12,560 --> 00:01:20,400
How bad is my hair right now? It's fine. The first thing you'll notice about the

17
00:01:16,240 --> 00:01:23,200
exive DC series is the size. It uses the

18
00:01:20,400 --> 00:01:29,920
same 3 and 1/2 in form factor as a typical desktop mechanical hard drive.

19
00:01:26,479 --> 00:01:32,880
By comparison, anything from uh a

20
00:01:29,920 --> 00:01:39,759
desktop SSD like this one all the way up to a highcapacity enterprisegrade SSD

21
00:01:36,079 --> 00:01:42,560
like this 7.68 TB one from Micron uses

22
00:01:39,759 --> 00:01:47,200
the 2 and 1/2 in form factor which back in the days when mechanical drives ruled

23
00:01:44,479 --> 00:01:52,399
the roost was only really used for laptops. It does this for a couple of

24
00:01:49,840 --> 00:01:57,360
reasons. Number one is that the Exad drive is really considered by the

25
00:01:54,880 --> 00:02:02,640
manufacturer to be more of a competitor for hard drives than it is for, you

26
00:02:00,000 --> 00:02:08,959
know, high performance SSDs like this PCI Express one over here from Liquid.

27
00:02:05,759 --> 00:02:11,360
Reason number two is this is just great.

28
00:02:08,959 --> 00:02:18,319
Look at this. They just need all that space. This has

29
00:02:15,200 --> 00:02:22,239
to be one of the most densely packed

30
00:02:18,319 --> 00:02:25,440
products that I have ever seen. It's

31
00:02:22,239 --> 00:02:28,239
nothing but floor to ceiling wallto-wall

32
00:02:25,440 --> 00:02:34,000
nan flash inside the entire enclosure. It's actually even heavy. I mean, most

33
00:02:31,040 --> 00:02:38,080
SSDs like they kind of don't really weigh anything. And if they do, it's

34
00:02:35,920 --> 00:02:43,040
just because they're using like a a big thick chassis so that it feels quality

35
00:02:40,160 --> 00:02:48,640
or whatever. This is not that far off the weight of an actual hard drive. But

36
00:02:45,840 --> 00:02:54,879
I guess that's just what it takes to get 100 terab of storage into a 3 and 1/2 in

37
00:02:52,080 --> 00:02:59,360
drive. To put that capacity in the appropriate context for y'all, okay?

38
00:02:57,200 --> 00:03:03,680
Like what's a what's a PC game that takes up an unfathomable amount of

39
00:03:01,200 --> 00:03:10,319
storage? Call of Duty War Zone. You could have 500 copies of War Zone on

40
00:03:08,319 --> 00:03:13,840
this drive. I mean, not quite, cuz it's going to be closer to like, you know, 90

41
00:03:12,239 --> 00:03:17,200
terabytes by the time you actually formatted an account for overhead.

42
00:03:15,440 --> 00:03:23,200
Obviously, I was being facitious just there. If you actually had 100 terab of

43
00:03:21,200 --> 00:03:28,480
game data, it would be way more economical to store it on a hard drive

44
00:03:25,680 --> 00:03:34,159
with a modestly sized solid state cache sitting in front of it. thing is a

45
00:03:30,959 --> 00:03:37,599
single user could never need low latency

46
00:03:34,159 --> 00:03:39,360
access to such an enormous and random

47
00:03:37,599 --> 00:03:46,000
distribution of data that they would need the entire library to be stored on

48
00:03:42,400 --> 00:03:49,120
solid state. Guys, you can only play one

49
00:03:46,000 --> 00:03:50,720
game at once, right? Well, except that

50
00:03:49,120 --> 00:03:56,640
time we played two games at once, but still even two. No justification for

51
00:03:53,519 --> 00:03:59,200
this. So, okay, let's play around with

52
00:03:56,640 --> 00:04:04,560
it, shall we? I've actually got autodisk benchmark running right now and you can

53
00:04:01,040 --> 00:04:08,480
see these numbers are

54
00:04:04,560 --> 00:04:14,560
not that impressive.

55
00:04:08,480 --> 00:04:17,759
Yep. At 512 bytes, we're looking at 9

56
00:04:14,560 --> 00:04:19,840
megabytes a second writes and 13.81

57
00:04:17,759 --> 00:04:25,680
megabytes a second reads. And in fact, getting all the way up to 1 2 and 4

58
00:04:23,120 --> 00:04:33,520
megabyte transfers, we are still sitting in the 300 to 450

59
00:04:29,360 --> 00:04:38,400
mgabytes a second range. So,

60
00:04:33,520 --> 00:04:42,400
wow. Considering that this is an SSD,

61
00:04:38,400 --> 00:04:45,680
that is not super fast. But but but but

62
00:04:42,400 --> 00:04:48,560
it's really big. So in the data center,

63
00:04:45,680 --> 00:04:54,639
the advantages of an approach like this are very real. The biggest one is

64
00:04:51,840 --> 00:04:59,600
unrivaled storage density. A Storinator XL like we used in our most recent

65
00:04:56,720 --> 00:05:05,280
Pabyte project holds 60 of these standard 3 and 1/2 in drives. Now with

66
00:05:02,800 --> 00:05:12,320
the 16 TBTE drives that we're using today, one of those units gives us about

67
00:05:08,639 --> 00:05:15,440
1 pabyte of RAW space in a 4U chassis.

68
00:05:12,320 --> 00:05:17,600
That's about 75 pabytes of accessible

69
00:05:15,440 --> 00:05:23,680
space after accounting for RAID redundancy and other ZFS overhead. By

70
00:05:20,880 --> 00:05:31,440
comparison, one of those chassis full of these puppies gives us six pabytes of

71
00:05:27,919 --> 00:05:34,560
raw capacity and over 5 pabytes of

72
00:05:31,440 --> 00:05:38,800
usable capacity as long as we've got a

73
00:05:34,560 --> 00:05:41,360
cool $2.4 million for the drives alone.

74
00:05:38,800 --> 00:05:45,360
But don't let that price fool you into thinking that there's no market for

75
00:05:42,880 --> 00:05:51,360
these things. Increasing your storage density by 5 to 6x has some very real

76
00:05:49,440 --> 00:05:58,240
advantages. Starting with the fact that you will need fewer servers to plug them

77
00:05:53,680 --> 00:06:01,360
into. Now, in the context of $2.5

78
00:05:58,240 --> 00:06:03,680
million worth of drives, the 10 grand or

79
00:06:01,360 --> 00:06:08,240
so that you might save per server box might not sound like a big advantage.

80
00:06:05,600 --> 00:06:14,000
But this is the but wait there's more moment. Fewer servers also means less

81
00:06:11,600 --> 00:06:18,880
expensive data center rack space and less rack space means less cooling. Each

82
00:06:16,720 --> 00:06:22,720
of these sucks back about 8 watts while idle and 16 watts while active. That's

83
00:06:21,280 --> 00:06:27,440
16 watts. That's the reason we actually had this fan on here while we were

84
00:06:24,479 --> 00:06:31,280
running benchmarks. Possibly the biggest possible savings is that depending on

85
00:06:29,600 --> 00:06:35,120
what kind of software you're running, enterprise licensing, which can be

86
00:06:32,960 --> 00:06:41,280
thousands or tens of thousands of dollars per year, is often handled on a

87
00:06:37,360 --> 00:06:43,680
per server or per CPU socket basis.

88
00:06:41,280 --> 00:06:48,880
Meaning that if you can consolidate your server count from five down to one over

89
00:06:46,639 --> 00:06:52,880
a span of 5 years or more, those recurring costs could end up eating a

90
00:06:51,120 --> 00:06:59,039
lot of the savings that you would get by going with hard drives. Not to mention

91
00:06:54,960 --> 00:07:01,440
that the performance of an all SSD setup

92
00:06:59,039 --> 00:07:07,759
versus all hard drives is going to be in another league, even if that's not that

93
00:07:03,840 --> 00:07:10,080
impressive for a modern SSD. Now, as I

94
00:07:07,759 --> 00:07:14,960
mentioned before, a lot of that ground could be made up with a higher speed SSD

95
00:07:12,800 --> 00:07:20,000
tier sitting in front of your spinning rust. But if you're working with, I

96
00:07:17,919 --> 00:07:24,400
don't know, let's say, uh, a gigantic scientific data set where you have no

97
00:07:22,400 --> 00:07:30,960
way of predicting what's going to be accessed next, an all SSD setup will

98
00:07:28,160 --> 00:07:36,000
have a latency advantage, which can even help improve CPU utilization efficiency

99
00:07:33,199 --> 00:07:40,160
because the system will spend less time waiting around for a slow storage

100
00:07:38,400 --> 00:07:45,280
subsystem. It can even help with reliability. One of the scariest parts

101
00:07:42,880 --> 00:07:50,560
of any server maintenance project is rebuilding a failed or degraded drive in

102
00:07:48,560 --> 00:07:54,560
a RAID array. And this is especially true with mechanical drives. These

103
00:07:53,280 --> 00:08:00,319
things have reached the point where their capacities are so high and the

104
00:07:57,919 --> 00:08:06,160
speeds that you can access them at are so low that the wear and tear on them

105
00:08:03,280 --> 00:08:11,840
during a rebuild increases the odds of a subsequent failure during the rebuild to

106
00:08:08,800 --> 00:08:15,520
the point where it is not trivial. Well,

107
00:08:11,840 --> 00:08:18,479
an exad drive like any SSD has no moving

108
00:08:15,520 --> 00:08:22,400
parts. It has higher random performance and it's got higher sustained speeds

109
00:08:20,879 --> 00:08:28,240
reducing the time for these risky operations.

110
00:08:24,240 --> 00:08:30,800
So, that all sounds great, but there are

111
00:08:28,240 --> 00:08:34,880
definitely some gotchas. And I mean, aside from the price, Nimbus Data here,

112
00:08:33,440 --> 00:08:42,640
I've actually got their data sheet right here. Nimbus Data boasts a fiveyear

113
00:08:38,959 --> 00:08:45,600
warranty with unlimited drive rights per

114
00:08:42,640 --> 00:08:52,800
day. Wow. How on earth are they doing that? Unlimited, my friends. Are they

115
00:08:49,680 --> 00:08:56,880
using some kind of special flash that

116
00:08:52,800 --> 00:09:01,360
that doesn't wear out? Is it magic SSDs?

117
00:08:56,880 --> 00:09:04,240
No. No, it's not. So, uh, whatever. This

118
00:09:01,360 --> 00:09:11,120
right here is a SATA interface, meaning that it's limited to 6 Gbit per second.

119
00:09:07,279 --> 00:09:15,200
By contrast, this right here is a liquid

120
00:09:11,120 --> 00:09:18,080
honey badger capable of over 50 times

121
00:09:15,200 --> 00:09:22,240
that speed. And like that's not necessarily a bad thing here. I mean,

122
00:09:20,720 --> 00:09:27,920
the honey badger is a very different product. It takes up a PCI Express 16x

123
00:09:25,279 --> 00:09:33,360
Gen 4 slot and can't reach nearly the capacity that an Exo drive can. All it

124
00:09:31,200 --> 00:09:39,040
means is that practically speaking, they can offer an unlimited write warranty on

125
00:09:36,320 --> 00:09:45,279
this thing because you cannot write data to it fast enough over that interface to

126
00:09:42,000 --> 00:09:48,720
wear out the 100 terabytes of NAND in 5

127
00:09:45,279 --> 00:09:51,200
years. It actually takes over 2 days of

128
00:09:48,720 --> 00:09:57,120
continuous sequential data writing to it in order to fill it up. Now, if you guys

129
00:09:54,880 --> 00:10:01,200
are anything like me, this is the part of this video you were waiting for. Not

130
00:09:59,040 --> 00:10:05,920
all this theoretical monkey business and all that nonsense. Lionus, when are you

131
00:10:04,160 --> 00:10:10,160
going to open the thing up and show us how it ticks

132
00:10:07,839 --> 00:10:14,720
right now? Now, it's not strictly speaking part of our loan agreement for

133
00:10:11,920 --> 00:10:19,040
this drive to open it up. But the way that I see it, they had to know who they

134
00:10:17,040 --> 00:10:23,600
were dealing with. Okay, so Oh, wow. Not all the screws are

135
00:10:21,920 --> 00:10:29,600
the same. Better keep track of where those go. And there's just something

136
00:10:25,600 --> 00:10:31,600
about unlimited power.

137
00:10:29,600 --> 00:10:39,399
And besides, isn't it just delightfully naughty to void the warranty on a

138
00:10:33,680 --> 00:10:39,399
$40,000 product like that? Ready?

139
00:10:40,720 --> 00:10:46,079
Oh, interesting. Very interesting. See

140
00:10:44,399 --> 00:10:52,079
how that's kind of glossy on there like that? I thought that that might just be

141
00:10:49,760 --> 00:10:57,680
because there was some leftover residue from like a thermal pad or something.

142
00:10:54,480 --> 00:10:58,959
But there isn't. See, look. There's

143
00:10:57,680 --> 00:11:07,279
nothing on the underside of the enclosure. So, what this probably is, this is a

144
00:11:03,760 --> 00:11:10,480
strategy I've seen before, is

145
00:11:07,279 --> 00:11:12,959
um a method of wiping off the markings

146
00:11:10,480 --> 00:11:17,440
from these chips and then they've actually glued the outside of it to make

147
00:11:15,279 --> 00:11:23,279
it more difficult to reverse engineer the product.

148
00:11:19,680 --> 00:11:25,839
Very clever, Nimbus data. Very clever

149
00:11:23,279 --> 00:11:30,000
indeed. These look like standard SATA connectors here. And then some kind of

150
00:11:28,079 --> 00:11:35,360
power interface that I'm unfortunately not familiar with on each of these

151
00:11:32,160 --> 00:11:37,839
daughter boards. Requires quite a bit of

152
00:11:35,360 --> 00:11:42,240
stress on these posts here to pop these additional daughter boards up. So, okay,

153
00:11:40,720 --> 00:11:49,279
we'll take off the second one. Each of these is 25

154
00:11:45,440 --> 00:11:51,279
terab. Isn't that crazy?

155
00:11:49,279 --> 00:11:55,519
Okay. I don't like the strain that this is putting on this thing here. Is there

156
00:11:53,440 --> 00:11:58,399
a way to pop those posts out or something? Don't think of it in terms of

157
00:11:57,120 --> 00:12:04,480
how much money it's worth. Think of it in terms of the people need to see it.

158
00:12:01,200 --> 00:12:09,360
Just need to just pop.

159
00:12:04,480 --> 00:12:12,000
Come on. Come on. There we go. Okay. So,

160
00:12:09,360 --> 00:12:20,959
even though they're using what looks like um the same connector as like a U.2

161
00:12:17,519 --> 00:12:24,399
two NVMe drive here. You can actually

162
00:12:20,959 --> 00:12:26,800
see right on their PCB custom pin out do

163
00:12:24,399 --> 00:12:32,000
not insert SFF8639 cable

164
00:12:28,320 --> 00:12:34,560
backplane. This is what splits out to

165
00:12:32,000 --> 00:12:41,440
this. So here's all the SATA interfaces for the individual 25 TBTE uh kind of

166
00:12:39,040 --> 00:12:46,639
slices. Now, this one I'm pretty sure it would

167
00:12:43,760 --> 00:12:51,360
be fairly rude of me to show because compared to the slices, this seems to be

168
00:12:49,440 --> 00:12:57,040
where the actual brains is. But I'm going to look at it. Yep, we're looking

169
00:12:53,600 --> 00:13:00,639
at an Altera FPGA.

170
00:12:57,040 --> 00:13:02,560
Looks like some memory. There is some

171
00:13:00,639 --> 00:13:06,560
very custom logic being done here. That's a That's not a cheap processor. I

172
00:13:05,360 --> 00:13:12,560
figured out how they assemble it, Brandon. These posts, they unscrew.

173
00:13:10,399 --> 00:13:17,600
There's absolutely no reason whatsoever to uh put all that strain on them. Wh

174
00:13:15,600 --> 00:13:22,720
Hey, there it goes. Uh I don't remember what order they were in, so um hopefully

175
00:13:20,079 --> 00:13:28,560
that doesn't matter. But yeah, you just put the sicey slices on there. 10 out of

176
00:13:25,600 --> 00:13:33,440
10 slicy. I mean, imagine it. Okay, adding 25

177
00:13:31,519 --> 00:13:38,320
terabytes of storage to your computer is that easy. You just do it four times and

178
00:13:35,440 --> 00:13:43,360
bam, 100 terabytes. And then I can just screw this in into the bottom there. No

179
00:13:41,680 --> 00:13:47,519
problem. I'm sweating right now from taking this

180
00:13:45,200 --> 00:13:50,560
thing apart. See, I play it off like I'm like, "Yeah,

181
00:13:49,360 --> 00:13:56,800
yeah, you know, whatever." It's like, "Yeah, whatever." It's like SSD or whatever. But like,

182
00:13:54,399 --> 00:14:00,240
I do not want to break this. I'm pretty sure we're on the hook for it if I do.

183
00:13:58,399 --> 00:14:03,440
All right, moment of truth, then. Hey, there's a bunch of activity LEDs. I

184
00:14:01,680 --> 00:14:07,920
didn't actually notice those before. Oh, you know what? I bet if I uh I bet if I

185
00:14:06,240 --> 00:14:13,519
put them together in the wrong order, they probably need to at least be reformatted.

186
00:14:10,800 --> 00:14:17,440
I don't know what kind of logic that FPGA is programmed with, though. Like, I

187
00:14:15,440 --> 00:14:23,279
don't Maybe it's smart enough to just put it back together. It definitely

188
00:14:20,800 --> 00:14:27,199
don't see the capacity. D is not accessible. Let's just give it a quick

189
00:14:25,440 --> 00:14:32,079
reboot. I think this was right. Oh, look at

190
00:14:29,360 --> 00:14:36,399
that. We got a disc checking prompt. It's showing up in disk management. It's

191
00:14:34,000 --> 00:14:43,600
got the full capacity. What if we just delete the volume? H. Okay. Unallocated.

192
00:14:40,079 --> 00:14:45,279
New simple volume. Hey. Hey. Hold on.

193
00:14:43,600 --> 00:14:49,920
This all this all looks pretty normal. Let's do a quick format here. Oh, Jake

194
00:14:47,440 --> 00:14:55,040
did warn me. It takes a spicy minute to format. The system cannot find the file

195
00:14:52,480 --> 00:14:59,680
specified. Uh, that's not a great sign. Well, I guess they're going to have to

196
00:14:57,040 --> 00:15:05,920
sort out which order the things go on in. Bye.

197
00:15:03,360 --> 00:15:09,360
Boy, do you want 50 bucks and to finally learn what making money with money

198
00:15:07,519 --> 00:15:13,279
means? Trade Station is one of the top brokers to do just that. They make it

199
00:15:11,600 --> 00:15:17,600
easy because you can trade stocks anywhere with their award-winning mobile

200
00:15:14,959 --> 00:15:20,560
app and desktop app, TradStation 10. You can learn how to trade if you're

201
00:15:18,720 --> 00:15:24,480
starting from scratch or give yourself a refresher if you're a seasoned veteran.

202
00:15:22,399 --> 00:15:29,279
And it'll allow you to trade stocks like in your favorite companies like AMD or

203
00:15:26,560 --> 00:15:33,279
NVIDIA or even trade cryptocurrencies. They also have commission free trading,

204
00:15:31,040 --> 00:15:37,519
meaning that you keep what you make. So, give it a try today and you'll get $50

205
00:15:35,760 --> 00:15:41,920
when you fund your new account. That's like a 10% return already for doing

206
00:15:39,760 --> 00:15:45,240
practically nothing. Get all the details at tradstation.com/promo/lt.

207
00:15:45,680 --> 00:15:54,759
We're going to have that linked below. Are you roll? You're rolling. Yes.

208
00:15:49,040 --> 00:15:54,759
Autodisk benchmark. Hold on. Dive start.

209
00:15:55,680 --> 00:16:03,360
Oh, thank goodness it's working. Okay. I had the two top ones swapped. I I just

210
00:16:01,360 --> 00:16:08,079
totally brain farted and I put the I put the wrong ones in that wrong order. It's

211
00:16:05,839 --> 00:16:12,000
working. Everything's good. Uh, right. We can shoot the thumbnail now.