WEBVTT

00:00:00.080 --> 00:00:07.200
recently it was brought to my attention that some of my friends in the industry

00:00:04.240 --> 00:00:10.880
went out looking for a high-speed server for storing and editing their high-res

00:00:09.840 --> 00:00:14.240
video without checking in with me

00:00:13.120 --> 00:00:18.640
now i am far from the lone authority when it

00:00:17.039 --> 00:00:22.800
comes to this stuff so it's not like it's impossible to build something

00:00:20.560 --> 00:00:29.359
really awesome without my help snazzy Labs managed it just fine it's just also

00:00:25.920 --> 00:00:33.360
pretty easy to get completely taken for

00:00:29.359 --> 00:00:34.880
a ride and when i saw how much i justine

00:00:33.360 --> 00:00:39.280
mkbhd and jonathan from tld paid for their

00:00:38.000 --> 00:00:43.360
jellyfish well i wasn't mad i was just

00:00:42.480 --> 00:00:48.640
hurt and disappointed i mean guys here's the thing with the

00:00:47.280 --> 00:00:53.120
exception of tld actually didn't build him anything but for the others of you i

00:00:50.879 --> 00:00:57.760
put together reliable mass storage for you because that was

00:00:55.760 --> 00:01:03.760
what you said you wanted if you had just told me you want high

00:01:00.879 --> 00:01:06.960
performance at any cost come on guys it's me

00:01:05.600 --> 00:01:12.000
i got your back so i've channeled all of that frustration

00:01:09.920 --> 00:01:17.920
into today's video where in collaboration with our special guest

00:01:14.880 --> 00:01:20.159
patrick from serve the home great site

00:01:17.920 --> 00:01:23.600
by the way worth checking out after the video

00:01:21.119 --> 00:01:27.119
serve the home i'll be creating what i call

00:01:24.880 --> 00:01:33.600
the jellyfish fryer a faster more reliable and just plain

00:01:31.360 --> 00:01:37.200
better solution summer break just started but it's never too early to

00:01:35.119 --> 00:01:41.200
start looking for a new laptop for back to school every origin pc laptop is

00:01:39.520 --> 00:01:44.079
ready for whatever games or school projects you're going to tackle and you

00:01:42.640 --> 00:01:54.399
can check out their special deals at the link below

00:01:54.399 --> 00:02:00.799
so yeah guys those numbers you saw at the beginning of this video that was no

00:01:58.560 --> 00:02:05.280
typo that was correct a

00:02:01.560 --> 00:02:10.319
120 terabyte jellyfish costs its lucky

00:02:05.280 --> 00:02:12.000
owner about 35 000 us dollars and that's

00:02:10.319 --> 00:02:17.280
assuming that they don't require lumaforge's vague

00:02:14.319 --> 00:02:21.680
performance boost option or more than a handful of video editors connected to it

00:02:19.360 --> 00:02:28.239
but the thing is it gets even crazier than that not only does a 120 terabyte

00:02:25.040 --> 00:02:31.120
jellyfish not actually have 120

00:02:28.239 --> 00:02:36.080
terabytes of usable capacity it's closer to 80 by the time you account for the

00:02:33.440 --> 00:02:41.599
storage space that's lost to redundancy and the about 10 percent of extra

00:02:39.200 --> 00:02:44.879
reserved space that lumaforge has left to ensure that zfs functions correctly

00:02:44.080 --> 00:02:49.840
now here's the thing this pricing might not

00:02:47.280 --> 00:02:56.080
offend me so much if there was something magical about the jellyfish like i don't

00:02:52.560 --> 00:02:58.640
know if it used uh Intel ruler NVMe ssds

00:02:56.080 --> 00:03:02.159
and it fit into like a a ruggedized case that you could throw on your back as

00:03:00.400 --> 00:03:06.400
you're slogging through the jungle on an on location shoot or something like that

00:03:05.680 --> 00:03:11.599
but it's not special and to put it in

00:03:08.720 --> 00:03:17.840
context not only was i able to clutch together a solution that matches their

00:03:13.760 --> 00:03:21.440
pricing i was able to do it while still

00:03:17.840 --> 00:03:26.560
overpaying for my server the 45 drives

00:03:21.440 --> 00:03:28.080
tornado is not cheap and i outfitted it

00:03:26.560 --> 00:03:33.519
with all solid-state drives instead of mechanical

00:03:31.360 --> 00:03:37.760
ones at the same usable capacity and you don't even have

00:03:35.920 --> 00:03:42.239
to be a tech expert to build something like this because we went with an

00:03:39.840 --> 00:03:47.280
off-the-shelf bare bone server most of the work was done all i had to do was

00:03:44.720 --> 00:03:50.799
spend about 15 minutes shucking the drives from their packaging

00:03:49.360 --> 00:03:58.799
and popping them in here i did a separate video and with 27 of these 3.84

00:03:54.879 --> 00:04:02.400
terabyte iron wolf 110 nas ssds i've got

00:03:58.799 --> 00:04:04.640
over a hundred terabytes of raw

00:04:02.400 --> 00:04:08.159
solid state storage ready to go

00:04:06.799 --> 00:04:14.000
so from there all that was left to do was

00:04:10.720 --> 00:04:16.000
phone a friend to show us the right way

00:04:14.000 --> 00:04:21.680
to configure it because is it correct to say that configuring an SSD based nas is

00:04:19.359 --> 00:04:25.360
not the same as a hard drive based nas that's 100 true all right so you want to

00:04:23.520 --> 00:04:29.280
introduce yourself then sure hey guys i'm patrick from serve the home we

00:04:26.800 --> 00:04:32.720
started sth 10 years ago building solutions just like this and now we

00:04:31.199 --> 00:04:36.720
review server storage and networking hardware all the way from scrappy diy

00:04:34.800 --> 00:04:41.280
ebay stuff all the way up to high-end six-figure plus enterprise gear so i

00:04:39.199 --> 00:04:44.400
kind of assumed that we would be using freenas but in addition to that you came

00:04:43.199 --> 00:04:49.120
with a bit of a trick up your sleeve right i did okay why don't we begin

00:04:46.880 --> 00:04:53.280
though with the basic install sure okay so freenas installer super easy it

00:04:51.360 --> 00:04:56.960
actually automatically does this so you don't really need to do anything

00:04:55.040 --> 00:05:01.280
and you get some really kind of old-looking ascii yeah i feel like i'm

00:04:59.040 --> 00:05:06.880
like gaming 30 years ago so what we'll do is we're going to select two drives

00:05:03.520 --> 00:05:08.960
for our boot drives so these are the 250

00:05:06.880 --> 00:05:12.639
gig ssds that shipped with our stornado they are and then

00:05:10.880 --> 00:05:16.880
we're gonna go fancy and we're gonna do a fresh install would you like to put a

00:05:14.560 --> 00:05:20.320
password in sir sure make it easy password serve

00:05:18.880 --> 00:05:25.600
the home now that we're booted up and we're in the gui we can start to configure our

00:05:23.280 --> 00:05:29.680
server and yes it's more complicated than a jellyfish but i mean i think it's

00:05:27.680 --> 00:05:33.039
fair to say where are we at like 50 clicks

00:05:30.880 --> 00:05:36.560
less than that it's really not that hard now we'll go into a little bit more

00:05:34.400 --> 00:05:40.080
detail about how we're configuring this drives and patrick will probably talk

00:05:37.919 --> 00:05:44.880
about it in a blog post later on in the video but for now once this is done the

00:05:42.960 --> 00:05:47.759
big thing we need to do is apply that special script which is going to do a

00:05:46.479 --> 00:05:52.800
couple of things number one is it's going to apply some

00:05:49.680 --> 00:05:55.039
SSD specific optimizations that freenas

00:05:52.800 --> 00:05:59.759
intends to include in the next version of their software but that for now

00:05:57.280 --> 00:06:04.479
they've backported into this version for us to do this video the other thing it's

00:06:02.080 --> 00:06:09.120
going to do is it's going to change the way that these four 10 gigabit network

00:06:07.600 --> 00:06:15.120
ports on the back function to be more like a jellyfish

00:06:12.880 --> 00:06:20.960
so this is basically sacrilegious in the networking world but

00:06:18.479 --> 00:06:26.160
the way we want this to work is such that if i were to take a network cable

00:06:23.919 --> 00:06:30.080
plug it into the back of my nas and then plug the other end into let's

00:06:28.720 --> 00:06:34.560
say like a a Thunderbolt 10 gig network adapter and

00:06:33.039 --> 00:06:39.280
a laptop i could just connect directly to this

00:06:36.720 --> 00:06:44.160
thing like it's a big old gigantic high-performance usb drive now

00:06:42.560 --> 00:06:47.680
that's not the typical way you would do things no it's definitely not and what

00:06:46.080 --> 00:06:51.039
was the reaction you got from industry professionals when you asked them to do

00:06:50.160 --> 00:06:56.720
this well my first reaction when we talked about it was i said wait you want to do

00:06:55.280 --> 00:07:01.840
what so for 20 plus years the industry has said no

00:07:00.000 --> 00:07:05.840
you use switches and those switches allow you to scale out and use more

00:07:03.840 --> 00:07:10.000
clients you have can have more security features i mean it's it is the way that

00:07:07.759 --> 00:07:12.639
you handle this type of situation when you have a high performance storage of

00:07:11.440 --> 00:07:17.840
multiple clients so i'm going to give the counter argument to that because the way that i

00:07:15.840 --> 00:07:21.680
see it when you're dealing with a techie person or

00:07:19.120 --> 00:07:27.120
a sysadmin type person on site that's managing let's say a video production

00:07:24.560 --> 00:07:31.120
sure switches are the way to go no doubt about it but if you've got people that

00:07:29.360 --> 00:07:35.680
are accustomed to just plugging in an external drive and

00:07:32.960 --> 00:07:40.639
working off of their laptop well i'd say that it's not crazy to

00:07:38.080 --> 00:07:45.919
imagine that it's far lower friction to say look it works exactly the way you're

00:07:42.880 --> 00:07:48.319
used to you plug in one cable you plug

00:07:45.919 --> 00:07:51.440
in one cable and you have access to your storage

00:07:49.360 --> 00:07:57.919
except instead of a Thunderbolt cable you use this weird thing so that's it

00:07:54.160 --> 00:08:00.000
we've got a healthy 26 drive raid z2

00:07:57.919 --> 00:08:04.479
with a hot spare so in the event that any one of those drives fails

00:08:01.840 --> 00:08:07.240
it starts rebuilding it immediately and you might notice that capacity looks a

00:08:06.240 --> 00:08:12.800
little low 77.91 tib so those are tibi bytes if we

00:08:11.360 --> 00:08:18.479
convert that to terabytes that's actually 85.6 terabytes so we are coming

00:08:15.759 --> 00:08:23.039
in right around the same capacity as the jellyfish for actually a slightly lower

00:08:22.080 --> 00:08:30.479
price because we're like 900 less or something like that okay we

00:08:28.000 --> 00:08:34.399
should be ready to connect directly to the back of our nas here

00:08:32.479 --> 00:08:37.919
transfer some files do some video editing wow

00:08:36.719 --> 00:08:41.680
can look at that even with the eight core core i9 you still spike it when

00:08:40.159 --> 00:08:48.240
you're just opening up a project like this um and wow we we peaked at around

00:08:45.120 --> 00:08:49.839
two and a half gigabit per second

00:08:48.240 --> 00:08:54.480
so scrubbing is actually not that demanding as we go

00:08:52.160 --> 00:08:58.160
through this 8k footage here so we're sitting right in the neighborhood of one

00:08:56.399 --> 00:09:01.680
and a half to two gigabit per second while playing back looks like it settled

00:09:00.000 --> 00:09:04.959
in a little bit lower than that let's speed up our playback

00:09:03.360 --> 00:09:11.200
that's gonna hurt you okay so it's not a terribly impressive demo

00:09:08.080 --> 00:09:12.480
because it's just one 4k stream but the

00:09:11.200 --> 00:09:17.600
nas works i think we need to kick this up a notch we do

00:09:15.279 --> 00:09:21.880
so we just completed our 12 machine lan center these are all

00:09:20.880 --> 00:09:28.480
ryzen 2700xs they've all got 10 gig lan

00:09:25.040 --> 00:09:31.360
and we're gonna grab ourselves a few

00:09:28.480 --> 00:09:37.680
quad 10 gigabit mix connect all of them at the same time and see just how many

00:09:34.959 --> 00:09:40.000
video streams we can do alright

00:09:38.880 --> 00:09:44.560
so there it is four Ethernet cables

00:09:45.360 --> 00:09:52.480
and theoretically we fire this up

00:09:49.519 --> 00:09:57.600
and we have access to it we

00:09:54.480 --> 00:09:57.600
we fire this up

00:10:00.320 --> 00:10:05.839
well that'll help we

00:10:06.240 --> 00:10:14.000
fire this up and we'll have access to it

00:10:10.959 --> 00:10:16.000
so we've got three links running through

00:10:14.000 --> 00:10:19.519
our switch down there that are in an lacp group so that's basically link

00:10:18.320 --> 00:10:25.000
aggregation so that's for a total of 40 gigabit plus

00:10:21.920 --> 00:10:28.320
40 plus 40 so that would be

00:10:25.000 --> 00:10:30.560
120 gigabit so that is effectively the

00:10:28.320 --> 00:10:33.920
same as if we had three of those quad ports and they were just plugged

00:10:31.440 --> 00:10:38.240
directly into the back of the computers then all of our machines are plugged

00:10:35.760 --> 00:10:42.240
into the switch and we've loaded up adobe premiere trials

00:10:40.399 --> 00:10:47.760
on each one of these machines with the intention

00:10:43.519 --> 00:10:51.839
of hitting all 12 of them at once

00:10:47.760 --> 00:10:54.480
and seeing just how many 4k video

00:10:51.839 --> 00:10:58.560
streams our server can handle so uh Jake

00:10:55.920 --> 00:11:02.000
oh you're already on it look at him go these young kids today they got so much

00:11:00.240 --> 00:11:07.680
energy you know so just as a recap here guys this is 16

00:11:05.200 --> 00:11:11.360
mpeg-2 files that were encoded at 100 megabit per second so that would be

00:11:09.120 --> 00:11:16.720
comparable to what you would record in the 4k high quality preset on something

00:11:14.320 --> 00:11:22.240
like an a7s2 now you can see here that this

00:11:19.760 --> 00:11:26.800
is a freaking lot of bandwidth especially when we have a lot of motion

00:11:24.320 --> 00:11:30.000
across all the clips and we can spike as high as four to even five gigabit per

00:11:29.040 --> 00:11:36.240
second and that's why we are just playing back

00:11:34.240 --> 00:11:39.200
never mind if we want to scrub through the footage

00:11:37.519 --> 00:11:43.680
if we scrub through the footage we are actually going to be able to saturate

00:11:41.600 --> 00:11:47.839
our 10 gigabit link here so you can see i'm sitting in the nine to nine and a

00:11:46.240 --> 00:11:53.360
half range isn't that absolutely beautiful but

00:11:50.800 --> 00:11:57.120
performance is still smooth this is actually a shockingly good editing

00:11:55.760 --> 00:12:00.720
experience this is it moment of truth you ready are

00:11:59.040 --> 00:12:06.079
you just doing that one no i'm gonna do all of them oh you ready yeah okay

00:12:04.800 --> 00:12:11.040
one two oh crap this one's at one quarter res

00:12:09.519 --> 00:12:14.720
oh they're all at one quarter road dang it no one quarter res is not good enough

00:12:12.880 --> 00:12:20.020
for us okay changing the res start

00:12:17.120 --> 00:12:21.920
start so all six of mine are going

00:12:21.920 --> 00:12:27.680
are we dropping frames or is it smooth looks pretty damn smooth looking pretty

00:12:26.160 --> 00:12:33.440
smooth to me okay so i got our overall feed here

00:12:30.639 --> 00:12:38.000
nice nice how we doing it's a casual

00:12:34.800 --> 00:12:39.920
25 gigabit 25 gigabit i think we can do

00:12:38.000 --> 00:12:44.320
better so one challenge that we've got is that

00:12:42.000 --> 00:12:48.959
while we'd love to just throw more video streams at each one of these machines

00:12:46.639 --> 00:12:53.200
we're up against a technical limit within adobe premiere where it only

00:12:50.480 --> 00:12:58.399
allows 16 sources for this multi-cam setup and also up against a CPU limit so

00:12:56.399 --> 00:13:04.839
our CPU is actually sitting anywhere from around 70 up to 90 percent as we're

00:13:02.800 --> 00:13:09.360
going through and playing back all these files so clearly we can't just throw

00:13:07.680 --> 00:13:12.880
more streams per machine but what we can do to hit our network

00:13:11.839 --> 00:13:17.360
harder is scrub

00:13:14.880 --> 00:13:20.480
all the machines so i think we need some helpers

00:13:18.320 --> 00:13:26.160
okay so thank you gentlemen the test here is simple we are trying to suck as

00:13:23.279 --> 00:13:29.760
much bandwidth as we possibly can from the video server sitting on this

00:13:28.160 --> 00:13:34.639
chair over here now we're playing back 16 100 megabit

00:13:32.639 --> 00:13:37.440
streams per machine as it is

00:13:35.920 --> 00:13:43.760
but that's not enough that's only about 25 to 27 gigabit

00:13:40.639 --> 00:13:44.959
child's play so if we scrub through the

00:13:43.760 --> 00:13:49.040
footage we can get each of these machines to

00:13:46.959 --> 00:13:54.959
pull about nine to nine and a half gigabit and we want to see just how hard

00:13:52.320 --> 00:13:59.279
we can make it hurt okay so i'm peaking at around four gigabit per second on

00:13:57.120 --> 00:14:03.519
each of mine and we're looking at about 40 gigabit overall so i think our link

00:14:02.079 --> 00:14:09.519
aggregation is not working it's not working all right so the good news is we managed

00:14:06.800 --> 00:14:16.560
to play 184 4k video streams off of our server and

00:14:13.680 --> 00:14:19.600
we managed even to scrub around through them

00:14:17.440 --> 00:14:23.839
during that process the bad news is that it looks like

00:14:22.240 --> 00:14:28.560
unless we can get link aggregation working properly it would in fact

00:14:26.720 --> 00:14:32.720
be better to go straight out with uh

00:14:31.199 --> 00:14:37.040
10 gigabit connections to each of the computers i just didn't feel like

00:14:34.639 --> 00:14:41.360
spending the couple thousand dollars on a bunch of those quad 10 gig cards so

00:14:39.680 --> 00:14:45.040
we're gonna call this we're gonna call this good enough for now

00:14:43.199 --> 00:14:49.440
so that's a pretty cool demo if you're into editing video off of a shared

00:14:47.680 --> 00:14:54.399
storage resource and it's actually pretty similar to the one that lumaforge

00:14:51.440 --> 00:14:58.160
used when they launched the jellyfish just

00:14:55.519 --> 00:15:03.360
bigger and badder because it's all flash and somehow at the same price

00:15:01.120 --> 00:15:08.480
but we haven't even addressed some of the other really cool things about this

00:15:05.680 --> 00:15:13.760
configuration yet so lumaforge is using two striped raid z2s so that's kind of

00:15:11.760 --> 00:15:18.959
like raid 60. so a stripe of raid sixes and that means

00:15:16.720 --> 00:15:23.360
that they can suffer anywhere from two to four physical drive failures before

00:15:21.199 --> 00:15:29.519
they lose any data now we can only take two drive failures

00:15:27.360 --> 00:15:35.279
and then a third assuming that one of them manages to rebuild with our hot

00:15:31.279 --> 00:15:36.959
spare so one to three over time that's

00:15:35.279 --> 00:15:40.639
kind of similar i guess but the story is a little bit more

00:15:38.639 --> 00:15:46.720
nuanced than that so patrick you guys have a calculator that people can use to

00:15:43.519 --> 00:15:49.440
calculate what the expected time to data

00:15:46.720 --> 00:15:53.360
loss is for a particular configuration and what did we come out at with this

00:15:51.360 --> 00:15:59.199
one right here yeah this one we basically had less than a

00:15:55.920 --> 00:16:02.000
.02 chance to have it fail

00:15:59.199 --> 00:16:05.440
over the next 10 years so we think it's pretty reliable and part of that is

00:16:04.079 --> 00:16:09.120
really just the fact that the hard drives are a lot slower than the ssds

00:16:07.360 --> 00:16:13.839
when it comes to rebuild which means that even if a drive fails your array

00:16:12.160 --> 00:16:18.079
spends less time in a degraded and vulnerable state than

00:16:16.480 --> 00:16:22.320
if you're using hard drives a couple other advantages of ssds are

00:16:20.320 --> 00:16:26.880
that these ones are about a hundred times less likely to read a bit

00:16:24.800 --> 00:16:32.320
incorrectly compared to even reliable hard drives and they've got

00:16:29.759 --> 00:16:36.720
some other practical advantages too no vibration no noise and if you're on the

00:16:35.360 --> 00:16:40.560
go like you're uh you know if you were to put something

00:16:38.399 --> 00:16:44.240
like mechanical hard drives on the back of a jeep in the jungle for an on

00:16:42.720 --> 00:16:48.560
location shoot that is a super bad idea and this

00:16:46.880 --> 00:16:51.680
wouldn't be nearly as vulnerable to those kinds of vibrations which by the

00:16:50.560 --> 00:16:56.079
way yes do kill drives you were telling a story

00:16:54.160 --> 00:17:00.399
about yahoo a little while ago oh yeah yahoo a long time ago

00:16:57.920 --> 00:17:03.759
actually put drives on storage arrays that were going across the parking lot

00:17:02.399 --> 00:17:06.640
and one of the things they found was that when they got the systems powered

00:17:05.600 --> 00:17:10.319
up and the drives powered up on the other end they had a big problem with

00:17:08.720 --> 00:17:15.280
drive failures and the reason for that was that those carts were actually using

00:17:12.799 --> 00:17:19.520
solid casters and that caused so much vibration that the hard drives ended up

00:17:17.039 --> 00:17:24.000
failing so that's like a good example of why hard drives even though they're

00:17:22.160 --> 00:17:26.799
generally reliable even you know if they get a little bit shaken up while they're

00:17:25.679 --> 00:17:32.880
powered off a lot less reliable than solid state drives in that scenario so we're not

00:17:30.559 --> 00:17:37.520
actually necessarily done yet we had some further optimization ideas i mean

00:17:34.880 --> 00:17:42.480
patrick really really wants to use a switch because as we saw unless you have

00:17:40.640 --> 00:17:46.720
a ton of streams coming into a single machine you're nowhere near 10 gigabit

00:17:44.559 --> 00:17:50.000
needed for each individual station but that's going to come down to you know

00:17:48.080 --> 00:17:55.679
how the user wants to use it for now we were trying to just go after well here

00:17:52.480 --> 00:17:57.440
you can have this but diy we could also

00:17:55.679 --> 00:18:02.480
get better performance and lower power consumption by using more modern cpus

00:18:00.480 --> 00:18:07.679
caching was something that we talked about and it's something that lumaforge

00:18:04.640 --> 00:18:09.760
actually offers as a performance boost

00:18:07.679 --> 00:18:13.440
option for the jellyfish they add an octane right cache

00:18:11.360 --> 00:18:18.720
with some more RAM and then we think maybe faster cpus they wouldn't confirm

00:18:16.000 --> 00:18:23.200
that for me uh for an extra 3 500 but you recommended against using something

00:18:21.200 --> 00:18:26.400
like an octane right cache for an all SSD based machine can you explain why

00:18:24.799 --> 00:18:29.520
that is yeah so you tend to use caching drives

00:18:28.559 --> 00:18:34.559
especially when you're going to hard drive and the idea was you have something that's faster than hard drives

00:18:32.400 --> 00:18:38.080
that's able to absorb random reads random writes and then smooth it out so

00:18:36.400 --> 00:18:41.360
it's more similar right so it's more sequential and better for the way that

00:18:40.000 --> 00:18:48.000
hard drives like to be accessed but solid state drives are different than hard drives and because of that you tend

00:18:44.559 --> 00:18:50.160
not to put as much caching in front of

00:18:48.000 --> 00:18:55.039
solid state race and so in this case we just didn't think that we needed it

00:18:52.160 --> 00:19:00.480
all right so we maybe aren't quite done but that is it for today but the sort of

00:18:58.160 --> 00:19:03.440
wrap up for this video is a bit long but it's also really important so try not to

00:19:02.000 --> 00:19:10.160
tune out guys we did this video for a couple of reasons one was to demystify some of the

00:19:07.600 --> 00:19:16.880
marketing mumbo jumbo that goes on with solutions like the jellyfish compatible

00:19:13.120 --> 00:19:16.880
with mac Linux and pc

00:19:17.120 --> 00:19:23.600
what does that even mean of course it is it's a commodity nas running free open

00:19:22.000 --> 00:19:29.120
source software but the other reason was to acknowledge

00:19:26.480 --> 00:19:32.559
that while we do prefer to do things our way

00:19:29.919 --> 00:19:36.160
that doesn't mean that our way is right for everyone and in fact even between

00:19:34.720 --> 00:19:42.240
the two of us and ix systems support staff

00:19:38.799 --> 00:19:44.240
we still ran into a few hiccups today

00:19:42.240 --> 00:19:50.400
so then i actually reached out to marquez mkbhd to send over a couple

00:19:47.440 --> 00:19:54.640
short clips explaining why the jellyfish has been great for him

00:19:52.480 --> 00:19:58.720
what's up Linus i'm kbhd here so there were a couple things that the jellyfish

00:19:56.000 --> 00:20:02.640
did specifically in the mkbhd studio to make our lives easier the setup being

00:20:01.200 --> 00:20:07.440
one of the biggest ones so this thing was out the box and operational within

00:20:05.919 --> 00:20:12.960
90 seconds like it had all the drives installed already everything was fresh out the box all we really had to do was

00:20:10.960 --> 00:20:17.919
install the jellyfish app on every computer that we wanted it to be on

00:20:14.880 --> 00:20:20.160
that's three in my case plug it in hit

00:20:17.919 --> 00:20:23.039
the on button and everything set itself up and then we actually had some

00:20:21.200 --> 00:20:26.880
assistance from the lumaforge team as far as setting it up to make sure it

00:20:24.320 --> 00:20:30.480
would work perfectly with final cut pro projects so workflow tips essentially so

00:20:29.200 --> 00:20:34.960
they definitely went above and beyond with that but really truly the beauty of

00:20:32.240 --> 00:20:38.240
it was going from not having any solution for working on videos at the

00:20:37.120 --> 00:20:42.400
same time to the next day having one and being

00:20:40.720 --> 00:20:45.280
able to edit you know close a project on one machine open it up on the other and

00:20:44.000 --> 00:20:49.440
keep going that was something we were able to do

00:20:47.520 --> 00:20:52.559
very quickly and seamlessly because the jellyfish i think at the end of the day

00:20:50.720 --> 00:20:56.559
when it comes to spending a bit more for a better overall solution for us than

00:20:54.960 --> 00:21:00.640
better hardware it can look a lot like the car

00:20:58.799 --> 00:21:04.880
enthusiast market like some people will buy a certain type of car because they

00:21:03.280 --> 00:21:07.440
know that will be a great tuner and they'll be able to get more horsepower

00:21:06.559 --> 00:21:11.919
out of it and work on it and get better numbers but they know that's that's more time

00:21:10.799 --> 00:21:17.200
they're going to spend because that's their hobby but some people just want to

00:21:14.320 --> 00:21:20.720
drive to work every day and back and grocery shopping and pick up the kids

00:21:18.640 --> 00:21:26.000
this just needs to be reliable and they will spend more on a car that's new just

00:21:24.080 --> 00:21:31.120
to do that and they can go to the dealer if something breaks down for convenience

00:21:27.840 --> 00:21:33.679
to fix it and that may seem lazy to the

00:21:31.120 --> 00:21:37.039
first person but that's just the way it is that's what the jellyfish is so i am

00:21:35.360 --> 00:21:41.039
fully aware that there are buildable solutions out there that will do better

00:21:38.960 --> 00:21:45.440
numbers and better read write speeds and things like that probably even a better

00:21:42.320 --> 00:21:47.360
looking box than the jellyfish but

00:21:45.440 --> 00:21:51.360
we've been too busy editing videos off of it to think about any of that so

00:21:49.520 --> 00:21:56.400
that's where we're coming from so in defense of lumaforge then it's easy to

00:21:54.159 --> 00:22:01.039
use when i called them they picked up the phone immediately they offer support

00:21:58.880 --> 00:22:05.440
plan with next day replacement drive so that two years down the road you don't have

00:22:03.200 --> 00:22:09.760
to remember all the ips of everything and how to do anything like companies

00:22:07.840 --> 00:22:13.600
like this do need to charge a premium so they can continue to provide support

00:22:11.760 --> 00:22:18.559
they offer a complete package so you can just forget about it like you're not

00:22:15.280 --> 00:22:20.559
buying a box you're buying a solution

00:22:18.559 --> 00:22:24.480
and in fairness to them the hardware that they're shipping is not

00:22:22.400 --> 00:22:28.559
actual garbage it's not one of those things where they're charging an

00:22:25.520 --> 00:22:30.159
enterprise price for you know

00:22:28.559 --> 00:22:36.640
like a sticker that they applied to something consumer grade like they're

00:22:32.240 --> 00:22:39.520
using zfs they're using centos this is

00:22:36.640 --> 00:22:42.880
truly good stuff their connector and manager is really simple to use if you

00:22:41.679 --> 00:22:48.240
have to set up a new share or something there's no command line required and

00:22:45.520 --> 00:22:53.120
also here's a crazy thing if you go to a major tier one storage vendor would you

00:22:50.559 --> 00:22:56.960
say that the pricing of the jellyfish is unheard of ludicrous it's perfectly in

00:22:55.360 --> 00:23:01.280
line with what you would see from a big vendor and they usually have great margins and they provide that solution

00:22:59.840 --> 00:23:06.240
and great support furthermore another thing people don't consider and

00:23:04.159 --> 00:23:10.880
i talked about this recently on lan show but in the film and production industry

00:23:08.720 --> 00:23:15.840
this kind of pricing is not about the hardware that you're

00:23:13.760 --> 00:23:19.600
getting it's more about the value that it provides

00:23:17.120 --> 00:23:25.039
like the amount of money that you're spending might be outrageous but given

00:23:22.400 --> 00:23:29.520
the amount of money that you will make if it works correctly and the amount of

00:23:26.960 --> 00:23:33.600
money you might lose if it doesn't work correctly

00:23:31.360 --> 00:23:36.480
maybe it's not that outrageous after all now we aren't going to be doing it that

00:23:34.880 --> 00:23:41.280
way as long as building our own machine is still possible but hey i felt like i

00:23:38.799 --> 00:23:45.039
had to say it anyway speaking of things i have to say the

00:23:43.120 --> 00:23:48.640
neighbor's app by ring yep that's the same ring that makes video doorbells is

00:23:47.039 --> 00:23:53.520
all about helping you stop feeling like you're alone when it comes to your security it allows you to receive

00:23:51.840 --> 00:23:57.840
real-time information on what's happening around you from other users so

00:23:56.480 --> 00:24:01.520
you can put out an alert if you see something suspicious like a possible

00:23:59.520 --> 00:24:05.919
burglar you can send a notice if you lost something valuable like your pet

00:24:03.679 --> 00:24:10.400
and you can even give or receive a warning if a disaster is coming your way

00:24:07.840 --> 00:24:14.480
like a fire or a flood ring partners up with local law enforcement to stop crime

00:24:12.400 --> 00:24:18.880
sprees and right now it's available in the us only but more countries are

00:24:16.640 --> 00:24:22.400
coming soon users have full control of what information is made publicly

00:24:20.480 --> 00:24:26.480
available to protect your privacy from both other users and law enforcement and

00:24:24.880 --> 00:24:30.320
it's free to use and download it's available for Android and iOS today so

00:24:28.880 --> 00:24:35.039
go check it out so thanks for watching guys massive

00:24:32.559 --> 00:24:38.480
thanks to patrick from serve the home guys go check them out

00:24:36.720 --> 00:24:41.679
go buy one of these tracker hats on their merch store you guys have a merch store

00:24:40.400 --> 00:24:46.799
you don't even you don't even sell them no these are limited edition so this is like exclusive exclusive check it all

00:24:45.120 --> 00:24:50.960
right so thanks to you guys for watching thanks to patrick for coming out here um

00:24:49.200 --> 00:24:54.000
if you guys like this video hit that like button get subscribed or maybe

00:24:52.720 --> 00:24:59.760
consider checking out where to buy the stuff we featured in the video description we were really happy with

00:24:57.440 --> 00:25:03.200
this tornado as well as our iron wolf naz ssds we're going to have links to

00:25:01.360 --> 00:25:07.120
those down there also link down there is our merch store which has cool shirts

00:25:04.720 --> 00:25:10.960
like this remember hard drives i remember

00:25:08.720 --> 00:25:14.640
like this as well as our Linus tech tips uh stealthity

00:25:12.720 --> 00:25:17.600
all right finally go join our forum that's down there too