WEBVTT 00:00:00.320 --> 00:00:07.600 we see a lot of Wild Tech around here but this this is the wildest we've seen 00:00:05.319 --> 00:00:13.240 in a long time like here's a question you need to ask yourself how many ssds 00:00:10.000 --> 00:00:16.320 do you need in your computer one 00:00:13.240 --> 00:00:20.920 two three how 00:00:16.320 --> 00:00:24.960 about 21 of them that's right we got it 00:00:20.920 --> 00:00:28.439 the Apex storage x21 it's absolutely 00:00:24.960 --> 00:00:31.439 cramp packed full of m.2 slots Each of 00:00:28.439 --> 00:00:34.840 which contains a Sab Rock ET 4 plus 88 00:00:31.439 --> 00:00:39.200 TB SSD that's right friends I'm holding 00:00:34.840 --> 00:00:42.079 a casual 168 tab of storage and this 00:00:39.200 --> 00:00:46.719 thing is so fast it shocked even the CEO of Apex storage just like I'm going to 00:00:45.039 --> 00:00:51.879 shock you with this message from our sponsor T get super affordable phone 00:00:49.879 --> 00:00:56.520 plans with awesome freebies and excellent customer service from T they 00:00:54.120 --> 00:01:00.519 were rated excellent by over 9,000 unbiased customer reviews on trust pilot 00:00:58.719 --> 00:01:06.600 so switch to T today by clicking the link in the video description be 00:01:02.960 --> 00:01:09.119 careful have you ever held 150 terabytes 00:01:06.600 --> 00:01:14.360 in the palm of your hand these things are worth more than my car and my car is 00:01:11.640 --> 00:01:20.040 new it's a 21 yeah he is a pretty good car kind of a car 00:01:17.200 --> 00:01:25.799 guy all right really the star of the show is this though there are only three 00:01:23.200 --> 00:01:29.920 of these cards in existence but if the buzz around it is anything to go by 00:01:27.439 --> 00:01:35.560 there's soon to be a lot more of them unlike some PCIe slot-based ssds the 00:01:32.960 --> 00:01:41.439 Apex storage x21 allows you to mix and match any commodity m.2 drives that you 00:01:38.880 --> 00:01:46.520 want and even upgrade them down the line because all you're doing is taking this 00:01:42.759 --> 00:01:49.320 PCIe by6 Gen 4 slot and splitting it up 00:01:46.520 --> 00:01:52.920 to all the attached drives and oh boy can you attach a lot of drives this 00:01:51.159 --> 00:01:59.560 controller at its heart can apparently handle up to a 100 PCI E lanes and the 00:01:56.600 --> 00:02:05.240 best part is you can install this in any m board you don't need a server board 00:02:02.240 --> 00:02:07.280 that supports PCI slot bifurcation all 00:02:05.240 --> 00:02:12.440 of that's handled on board and another feature I'm really excited about is that 00:02:09.080 --> 00:02:14.680 apparently you can hot swap the ssds on 00:02:12.440 --> 00:02:17.879 the board I don't want to do that we're going to have to try that don't want to 00:02:16.200 --> 00:02:22.360 do that we're going to have to try that I mean sabrent would want us to shout 00:02:20.239 --> 00:02:26.000 out sabr by the way they asked us hey if we send you those drives can you guys 00:02:24.000 --> 00:02:31.160 mention Us in the video I was like I will suck on your toes for this many 00:02:28.239 --> 00:02:36.760 drives so uh you'll find them Linked In the video description it's an SSD but it 00:02:34.640 --> 00:02:42.920 actually takes up as much space in your computer as a GPU and has the same 00:02:40.519 --> 00:02:47.879 number of power connectors okay there's six pin PCIe instead of 8 Pin PCIe but 00:02:45.879 --> 00:02:54.000 still how much power does this thing draw I don't think it's that much oh my 00:02:51.879 --> 00:02:58.000 God right I knew that I knew that these are over $1,000 but still it just didn't 00:02:56.159 --> 00:03:02.560 register yeah holy crap crap so what are they 00:03:00.840 --> 00:03:08.120 hold on a second what are they doing here this looks like it's got to be at 00:03:04.879 --> 00:03:10.959 least a PCIe by8 link this has got to be 00:03:08.120 --> 00:03:14.200 another PCIe by 16 actually looking closer at the layout of the 00:03:11.920 --> 00:03:18.920 daughterboard that makes sense this top slot here is routed to these four and 00:03:16.879 --> 00:03:24.159 these four on the back so a total of eight drives to this 6X slot and these 00:03:21.840 --> 00:03:28.280 four here are routed to the other one that gives us a probable total of two 00:03:26.040 --> 00:03:33.519 lanes per Drive which might seem like oh that's a bottleneck cuz this rocket 8 00:03:30.920 --> 00:03:38.280 tab can do 7 GB a second and that's only 3 and a half but when we consider that 00:03:36.239 --> 00:03:42.720 the system is accessing all these drives through a single PCIe by6 slot I don't 00:03:41.280 --> 00:03:46.239 think it's going to be a major factor for performance that is something we 00:03:44.480 --> 00:03:51.080 could test though by running a speed test on just one drive installed in the 00:03:48.799 --> 00:03:55.239 card we should do that hey oh sure yeah I kind of want to try it there's other 00:03:52.720 --> 00:03:58.920 stuff to look at here six pin PCIe power connector I mean should we pop the heat 00:03:57.200 --> 00:04:04.319 sink go for it I kind of want to look at it right I'm assuming we have to send 00:04:00.760 --> 00:04:06.599 this back hey I don't know oh who the 00:04:04.319 --> 00:04:10.319 heck are these guys it's so wild they come out of basically nowhere and 00:04:08.079 --> 00:04:16.440 they're like yep we've got more ssds than anyone else that's what you get for 00:04:12.480 --> 00:04:18.720 being asleep on the job switch Tech pfx 00:04:16.440 --> 00:04:23.320 I don't know why but I was like expecting an fpga or something I guess 00:04:21.320 --> 00:04:29.039 that makes sense that it wouldn't be since you're not really doing any logic 00:04:25.800 --> 00:04:31.960 on the board if it was some kind of raid 00:04:29.039 --> 00:04:35.360 card or something like that then maybe but if all this is doing is just PCIe 00:04:33.880 --> 00:04:40.160 switching then it doesn't have to be that maybe there's an fpga somewhere 00:04:37.880 --> 00:04:45.160 else no it looks like the whole thing is just this chip just this chip it's 00:04:42.960 --> 00:04:49.479 bigger than most CPUs I mean yeah well yeah yeah yeah I 00:04:46.560 --> 00:04:52.960 mean I'm not not undermining the coolness of the chip I'm just and where 00:04:51.440 --> 00:05:00.280 would we normally find something like this I'm imagining like a PCIe fabric 00:04:56.000 --> 00:05:04.880 like rack mount switch or something or 00:05:00.280 --> 00:05:08.000 I don't even know I I don't rightly know 00:05:04.880 --> 00:05:11.680 sir it can be used in Metro networks and 00:05:08.000 --> 00:05:13.759 core networking cellular infrastructure 00:05:11.680 --> 00:05:18.120 broadcast equipment I would imagine anyone building out composable PCIe over 00:05:16.479 --> 00:05:22.080 fiber infrastructure might use something like this man those things are wild you 00:05:20.120 --> 00:05:26.080 can have a whole bunch of PCIe devices just connected over fiber optic cables 00:05:23.960 --> 00:05:31.759 to a switch and then you can have your systems and then on the Fly you can 00:05:28.440 --> 00:05:34.880 assign I know put um six gpus in that 00:05:31.759 --> 00:05:37.960 one and it just connects to 00:05:34.880 --> 00:05:40.199 anyway okay and I do want to say the hot 00:05:37.960 --> 00:05:48.080 plug support that I said is on the data sheet for this chip not the data sheet 00:05:44.000 --> 00:05:50.360 for this whole solution well start with 00:05:48.080 --> 00:05:54.560 one which one's going to be the lucky slot here why would you start with one 00:05:52.880 --> 00:05:59.960 because I want to see if they each get two lanes oh yes well but you can just 00:05:58.360 --> 00:06:04.680 do that with all them on there yeah I just I want to see how it behaves with 00:06:01.360 --> 00:06:09.199 one okay okay this is awkward we need to 00:06:04.680 --> 00:06:11.680 move our GPU 4070 by the way 4070 ah all 00:06:09.199 --> 00:06:14.680 right let's turn it back on 00:06:15.039 --> 00:06:24.000 yeah you were here the whole time I did nothing you did touch it though I well I 00:06:21.479 --> 00:06:30.199 touched it so you want the GPU in now yep thing is uh oh you can't put it in 00:06:28.000 --> 00:06:37.919 this slot because then we get by eight and by eight all right we need all 16 00:06:34.479 --> 00:06:39.840 PCIe Gen 4 lanes for our SSD so I guess 00:06:37.919 --> 00:06:44.319 we're putting it in this 1X slot yes one sec that's the stupidest thing ever 00:06:41.919 --> 00:06:48.520 really does it does it touch something is it going to short out yes yeah I'm 00:06:47.080 --> 00:06:55.800 giving it a sec oh oh I don't think it got green before hold on 00:06:51.080 --> 00:06:58.800 hey patience all right this GPU is in at 00:06:55.800 --> 00:07:02.199 a very uncomfortable angle sir yeah I I 00:06:58.800 --> 00:07:04.639 don't love it and our one dis shows up 00:07:02.199 --> 00:07:09.960 oh I see you've did you configure this in a Windows software raid zero yes 00:07:07.840 --> 00:07:15.199 that's the stupidest thing I've ever heard and I love it all right let's uh 00:07:12.479 --> 00:07:19.759 we can also do the BIOS raid if you want that would be smarter although I've had 00:07:16.960 --> 00:07:24.680 some issues with AMD PCIe raid and you know reformatting Windows and getting 00:07:22.360 --> 00:07:27.440 confused and stuff so I don't know I mean if we're doing something we'd never 00:07:26.120 --> 00:07:32.919 recommend anyway it doesn't really matter how we do it 00:07:30.360 --> 00:07:39.960 so my theory my theory then is that this is only going to get us a buy two 00:07:35.280 --> 00:07:42.800 connection no wait how does that work 00:07:39.960 --> 00:07:47.919 it's claiming to be PCI gen 4x4 right but wait the connection 00:07:44.919 --> 00:07:49.159 through the PCI switch chip would be at 00:07:47.919 --> 00:07:53.680 least by four but then then the drive wouldn't 00:07:51.720 --> 00:07:58.520 report that okay let's just try yeah let's see what it does man if they wired 00:07:55.560 --> 00:08:04.479 every slot up for four lanes they did they wired every slot for four lanes 00:08:01.280 --> 00:08:07.000 that dramatically increases the cost but 00:08:04.479 --> 00:08:11.520 also dramatically increases the utility of this product because under normal 00:08:09.440 --> 00:08:16.120 circumstances you wouldn't do something dumb like configure 21 drives in a raid 00:08:13.919 --> 00:08:20.560 zero you would have this in a system that's got a lot of CPU resources as 00:08:18.720 --> 00:08:24.479 well and then you would be dividing up that Solid State Storage sometimes 00:08:22.120 --> 00:08:28.240 leasing it to separate clients so some of them might be using it when others 00:08:26.440 --> 00:08:33.080 aren't which means being able to get the full throughput to one Drive could 00:08:30.400 --> 00:08:40.200 matter depending on your use case that's pretty cool that's awesome let's add 00:08:35.240 --> 00:08:43.039 another Drive H please turn it off I 00:08:40.200 --> 00:08:49.440 don't seems like a really bad idea I'm a little nervous too please do 00:08:46.959 --> 00:08:52.399 remember each of these drives is $1,500 1,500 bucks 00:08:52.519 --> 00:09:00.040 hey oh let's get a cheaper one I think I 00:08:56.920 --> 00:09:02.440 have one in my backpack of course 00:09:00.040 --> 00:09:10.560 I mean why wouldn't I right don't you keep an SSD in your backpack 00:09:06.200 --> 00:09:13.160 hey Good Old Reliable crucial only 500 00:09:10.560 --> 00:09:15.560 gigs okay you're doing a great service for your 00:09:15.880 --> 00:09:23.720 country oh light turned on oh yeah that's something it's not there but also 00:09:20.920 --> 00:09:29.640 this is still working so I kind of consider that a 00:09:25.440 --> 00:09:32.760 win holy crap even though it was isn't 00:09:29.640 --> 00:09:37.680 doing anything it's like flipping hot oh 00:09:32.760 --> 00:09:42.920 wow I just installed 32 tab of SSD on 00:09:37.680 --> 00:09:46.640 here oh looks so good 1 2 3 4 5 6 7 8 9 00:09:42.920 --> 00:09:49.519 10 11 12 13 14 15 16 18 19 20 one hey 00:09:46.640 --> 00:09:55.640 they're all here sick and you can maybe changing that to 00:09:52.959 --> 00:09:59.800 raid changes it I don't actually know no it's 00:09:56.399 --> 00:10:04.040 somewhere oh but just 00:09:59.800 --> 00:10:06.320 just let it go past the BIOS oh oh wait 00:10:04.040 --> 00:10:10.200 what now do you see why I had a Windows raid well you have to physically remove 00:10:08.600 --> 00:10:14.560 the drives from the system we don't even have them configured in a raid you just 00:10:13.079 --> 00:10:21.279 can't in the BIOS it's too many for am5 this must be 00:10:18.279 --> 00:10:24.279 a consumer platform lock down thing 00:10:21.279 --> 00:10:27.560 because otherwise you could totally just 00:10:24.279 --> 00:10:29.519 run it does Intel let you do it I'm not 00:10:27.560 --> 00:10:33.519 entirely sure oh maybe what I said earlier about just 00:10:31.279 --> 00:10:40.720 being able to throw this in a nuck and boom SSD server isn't true then AMD 00:10:36.720 --> 00:10:42.639 locks it down buttheads man I'm 00:10:40.720 --> 00:10:46.920 disappointed you got to put this in a Server Motherboard what the average 00:10:44.600 --> 00:10:52.440 consumer doesn't have $2,800 to spend on an m.2 carrier card so AMD didn't think 00:10:49.720 --> 00:10:56.880 of that well I guess what I need to do then is go back into dis 00:10:54.839 --> 00:11:02.600 management and fix your raid that I broke yes oh boy this will be tedious 00:11:00.200 --> 00:11:07.680 oh can can you not just click like add to volume and it figures it out it's 00:11:05.320 --> 00:11:15.320 raid zero the volume is dead oh oh what haha okay it worked I 00:11:13.839 --> 00:11:24.040 have no idea what just happened there but I'm into it oh yeah oh yeah I'm 00:11:20.560 --> 00:11:27.920 going to call you Big 00:11:24.040 --> 00:11:30.480 D yes thank you for hitting quick format 00:11:27.920 --> 00:11:34.320 I did not hit that once it took like 5 hours it was 5:30 I was 00:11:32.320 --> 00:11:40.040 just like all right see you tomorrow and that's on ssds I've done 00:11:37.800 --> 00:11:45.800 that with hard drives before wait have you like actually run Windows raid zero 00:11:42.120 --> 00:11:48.160 in a system sort of I was running 00:11:45.800 --> 00:11:52.600 multiple raid cards running raid five Hardware raid five and then I raid 00:11:51.120 --> 00:11:57.880 zeroed them in Windows that's one of the early 00:11:54.360 --> 00:12:01.519 iterations of WX server 00:11:57.880 --> 00:12:04.360 actually this blows my mind wao you okay 00:12:01.519 --> 00:12:13.079 yep I'm fine okay this is the maximum speed of some things okay SATA 600 00:12:08.639 --> 00:12:17.519 megabytes a second okay PCIe 3.0 3.4 00:12:13.079 --> 00:12:22.320 single one of these drives 7 GB a second 00:12:17.519 --> 00:12:24.279 ddr4 25.6 GB per second all right these 00:12:22.320 --> 00:12:29.199 drives are already getting pretty toasty here I haven't even done anything yet we 00:12:27.040 --> 00:12:33.639 should get us we should get some Cooling on this or wait well yeah check the 00:12:30.760 --> 00:12:38.760 camera yeah let's check the camera first okay uh Alex that heat sinks at 90° all 00:12:37.079 --> 00:12:46.839 right let's uh that means the Chip's probably hotter uh yeah the fact that these 55° 00:12:44.199 --> 00:12:50.920 ssds didn't look hot in the frame is a bad thing well wait how are you even 00:12:48.920 --> 00:12:56.160 supposed to access any of the fan ports they're all down here there's a bunch of 00:12:53.320 --> 00:13:03.000 fan ports uh uh so do you want to zip tie that on the back here really yes so 00:12:59.360 --> 00:13:06.079 our method oh oh I see we're making like 00:13:03.000 --> 00:13:10.519 a tunnel yes with cardboard yes of 00:13:06.079 --> 00:13:14.560 course we are oh my God Alex what the 00:13:10.519 --> 00:13:17.639 hell what it's highly effective uh iip 00:13:14.560 --> 00:13:19.079 okay so what the hell is going on here 00:13:17.639 --> 00:13:27.079 it's fine it's fine you know this is barely in the slot right yeah what fan 00:13:22.720 --> 00:13:29.320 is that not as good as it was before 00:13:27.079 --> 00:13:34.760 what I found worked really well cuz I took one zip tie really well you say yes 00:13:31.680 --> 00:13:37.279 really well right up through there oh my 00:13:34.760 --> 00:13:42.320 God now one of those and I was The Reckless idiot for trying hot swap so 00:13:40.199 --> 00:13:47.279 that can go on there and then I found it worked really 00:13:44.480 --> 00:13:53.079 well if the other one went through the GPU um hold on I need another zip tie 00:13:51.160 --> 00:14:00.519 now I'm participating I'm officially party to this okay it's at 00:13:56.480 --> 00:14:04.680 74° okay y they're all at like 30 6 35° 00:14:00.519 --> 00:14:06.320 now down from 50 60 heck yeah nice it 00:14:04.680 --> 00:14:09.839 works okay gigabytes 00:14:12.399 --> 00:14:20.120 is now I want to make something clear just because that's as fast as a stick 00:14:17.279 --> 00:14:24.600 of memory and I don't even just mean you know theoretically when you're 00:14:21.320 --> 00:14:25.639 addressing it raw this is with file 00:14:24.600 --> 00:14:30.920 system overhead doesn't mean that you could use 00:14:27.839 --> 00:14:33.320 it as RAM the latency is going to be 00:14:30.920 --> 00:14:38.079 much much higher even if the bandwidth is off the charts unbelievable let's 00:14:36.360 --> 00:14:43.199 just have a look here oh yeah how many threads are we given it it looks like 00:14:40.160 --> 00:14:46.000 four four is kind of where it seemed the 00:14:43.199 --> 00:14:53.360 happiest in Windows oh okay so four for all uh sure we are right at the 00:14:49.600 --> 00:14:55.199 theoretical limit of this slot yeah I 00:14:53.360 --> 00:14:59.880 mean that's the thing right is we're putting so many drives behind it that 00:14:57.839 --> 00:15:05.800 the SSD control the Nan flash none of these bottlenecks 00:15:02.959 --> 00:15:10.759 exist anymore you're actually limited by the PCIe 00:15:07.199 --> 00:15:12.240 slot at least in sequential workloads as 00:15:10.759 --> 00:15:20.920 these random ones come up you're going to see oh wow 2 gbes a second is aing 00:15:15.519 --> 00:15:22.639 lot that's wow uh it's obviously nowhere 00:15:20.920 --> 00:15:27.560 near the capabilities of the slot we'd have to put 00:15:25.040 --> 00:15:33.199 another what what would that work out to about 200 drives on one of these 00:15:30.560 --> 00:15:38.240 carriers you know at a q depth of 32 in a random workload to really like 00:15:35.000 --> 00:15:39.880 saturate the PCI E slop but still now 00:15:38.240 --> 00:15:43.560 that I've said it I'm sure those wild people over at Apex storage are going to 00:15:41.480 --> 00:15:47.600 try and build one now it's worth noting you've seen speeds like this before in 00:15:45.160 --> 00:15:51.000 the past in fact with an inexpensive carrier board that relies on the 00:15:49.000 --> 00:15:55.560 motherboard to do the bifurcation and just four ssds you can put a benchmark 00:15:53.920 --> 00:16:00.959 numbers like this no problem that's actually what I was running in my old personal rig the issue though is can 00:15:59.199 --> 00:16:06.160 only see these kinds of numbers under ideal conditions when those ssds are 00:16:03.600 --> 00:16:10.839 acting in their SLC cache mode as soon as you hit them with any kind of 00:16:07.519 --> 00:16:13.199 sustained load especially a long right 00:16:10.839 --> 00:16:18.199 they are going to absolutely plumet with the x21 though having so many drives 00:16:15.880 --> 00:16:23.680 running in parallel we weren't able to change these numbers no matter how hard 00:16:20.560 --> 00:16:26.000 we hit the array oh wow it is actually 00:16:23.680 --> 00:16:30.639 using 100% of these discs at least if task manager is to be believed that is a 00:16:28.440 --> 00:16:36.519 lot of of data to be moving around in like 5 6 seconds yep I don't even know 00:16:34.199 --> 00:16:43.000 what to do to like show how fast it is cuz like what do we do check like an SSD 00:16:39.199 --> 00:16:44.600 in here or like an SD card is fast 00:16:43.000 --> 00:16:47.800 enough to keep up with it it's not fast enough that is way too slow there's no 00:16:46.600 --> 00:16:53.600 way we're going to be able to wait that long okay so we'll just fire up Linux 00:16:50.839 --> 00:16:58.560 sure all right the reason we're firing up Linux and doing this is not because 00:16:56.880 --> 00:17:02.920 we're expecting to see faster sequential speed I mean we were already at the 00:17:00.839 --> 00:17:07.400 theoretical limits of what that slot can do in Windows but in Linux we have a lot 00:17:05.559 --> 00:17:11.839 more control over our hardware and we are expecting to overcome some of 00:17:08.959 --> 00:17:17.199 Windows' limitations in terms of iops and iops are far more important for the 00:17:15.039 --> 00:17:23.079 kinds of applications that folks buying a carrier card like this might care 00:17:19.039 --> 00:17:25.919 about so things like databases or many 00:17:23.079 --> 00:17:30.840 many users accessing this storage all at the same time it's a measure of how many 00:17:28.400 --> 00:17:35.480 operation per second our storage array can perform assuming that every one of 00:17:33.000 --> 00:17:40.600 those transactions is very very small which is much more realistic for some 00:17:38.280 --> 00:17:43.880 context normal SSD is what like somewhere around a million like a really 00:17:42.360 --> 00:17:50.919 really good SSD honey badger was somewhere around 4 00:17:48.240 --> 00:17:54.679 to 6 million that's that was obscene really really fast especially at the 00:17:52.760 --> 00:18:00.840 time okay and 00:17:57.360 --> 00:18:00.840 go what the heck 00:18:03.120 --> 00:18:10.919 hell so this is very small files to get around the PCI limitations but it shows 00:18:08.360 --> 00:18:14.919 you kind of the upper limits of what we can expect like I alluded to when we 00:18:13.240 --> 00:18:18.960 were running tests in Windows this is without the burden of a file system it's 00:18:17.520 --> 00:18:25.520 going down yeah it's still stupid just wanted 00:18:22.520 --> 00:18:29.200 to check something can you think of any 00:18:25.520 --> 00:18:31.400 reason why our iops would gradually fall 00:18:29.200 --> 00:18:37.320 on this array as we run the test in Linux if it's doing any rights then it 00:18:34.200 --> 00:18:40.200 could be because of that oh is it doing 00:18:37.320 --> 00:18:44.679 rights is it doing rights I don't know um I'm not entirely sure how it's doing 00:18:42.200 --> 00:18:49.000 that right now but it could also be that it's heating 00:18:46.000 --> 00:18:50.480 up okay I suspect it's the rights thing 00:18:49.000 --> 00:18:54.840 I just wasn't sure if this test was actually writing to the 00:18:52.240 --> 00:18:58.960 drives yeah I'm not sure if it is either it seems to be kind of settling in now 00:18:56.600 --> 00:19:03.799 anyway and it's still at 40 million I Ops yeah I mean it could be that uh 00:19:01.559 --> 00:19:09.200 originally it was like really high uh bur because of like the the dam cach and 00:19:06.520 --> 00:19:15.280 all that kind of stuff but uh now it's settled into the natural iops all right 00:19:11.919 --> 00:19:18.240 see you later so I lied earlier then we 00:19:15.280 --> 00:19:22.919 did manage to overcome the SLC cache just it's still really fast I do kind of 00:19:20.960 --> 00:19:27.760 want to know where it ends up it seems like it's ending up here cuz it went 00:19:24.200 --> 00:19:30.559 slower and now it's gone faster oh yeah 00:19:27.760 --> 00:19:35.240 wow I thought it would just kind fall a lot I mean the speed of an individual 00:19:32.600 --> 00:19:39.320 Drive will fall by as much as like a tenth sometimes when it goes from cash 00:19:37.679 --> 00:19:44.080 mode to just like steady state where it has to do garbage collection in the 00:19:41.919 --> 00:19:48.600 background that's really fast there's just so much nand that it can do things 00:19:46.919 --> 00:19:53.919 in the background and still pump out these crazy numbers yep now as much fun 00:19:51.960 --> 00:19:57.320 as that was this is a serious tool for serious work and you're probably 00:19:55.120 --> 00:20:01.600 wondering well just what kind of serious applications are people using cards like 00:19:59.200 --> 00:20:05.000 this for we asked Apex storage and while they couldn't give us exact names they 00:20:03.520 --> 00:20:08.960 said that their pre-orders are from people who intend to use them for 00:20:06.679 --> 00:20:12.840 Enterprise data center like applications and this is to take advantage of the 00:20:10.400 --> 00:20:16.440 falling prices of flash right now uh think of something like a high 00:20:14.200 --> 00:20:20.559 performance version of back Blaze where they could use consumer hardware and 00:20:18.559 --> 00:20:24.679 then pass those cost savings along to the customers they also have pre-orders 00:20:22.760 --> 00:20:29.000 from folks in the digital forensic space who are excited by the size and speed 00:20:27.360 --> 00:20:33.159 with the ability to add cards into existing workstations and they've had 00:20:31.000 --> 00:20:37.840 interest from high-end performance users and video editors who are excited to use 00:20:34.960 --> 00:20:40.760 it with 4K and 8K footage other than the capacity I don't really see any reason 00:20:39.559 --> 00:20:46.480 why you would need this for video editing but sure there's apparently also 00:20:43.640 --> 00:20:50.760 people in the AI space since well you work with these giant data sets and if 00:20:48.440 --> 00:20:55.640 you've got spicy gpus we should Chia mine on 00:20:52.039 --> 00:20:57.919 it chew through a lot of data in general 00:20:55.640 --> 00:21:02.240 Apex summarized their customers as being really anyone one who spends a lot of 00:20:59.720 --> 00:21:06.280 time writing to and reading from discs the more iops and bandwidth that you 00:21:03.880 --> 00:21:09.640 need at this kind of capacity the more it's going to improve your Computing 00:21:07.720 --> 00:21:15.039 case uh some of which they probably haven't even thought of yet and I share 00:21:12.960 --> 00:21:20.640 your sentiment I'm also excited to see where people use these and I'm excited 00:21:17.559 --> 00:21:22.120 to tell you all about our sponsor T are 00:21:20.640 --> 00:21:29.000 you tired of feeling like you're stuck in a phone plan that doesn't meet your needs or is too expensive meet T 00:21:26.200 --> 00:21:32.720 Mobile's build your own plan with build your own plan you can create the perfect 00:21:30.880 --> 00:21:36.799 phone plan that suits your lifestyle and your budget they've got options like 2 00:21:34.880 --> 00:21:42.120 gigs plus unlimited talk and text for just $14 a month or unlimited everything 00:21:39.679 --> 00:21:46.760 for just $29 a month so you can enjoy affordable and flexible plans that suit 00:21:44.159 --> 00:21:52.000 you and that's not all T also offers freebies like hotspot Wi-Fi calling and 00:21:49.279 --> 00:21:56.240 unlimited texts plus with international calls to 60 plus countries and eim 00:21:54.320 --> 00:22:01.320 included you'll have everything you need in one plan and for families tell offers 00:21:59.200 --> 00:22:05.760 individual plans for each line with no shared balance or extra cost per line 00:22:03.520 --> 00:22:10.559 making it easy to manage multiple lines you can even have up to 10 lines on one 00:22:07.880 --> 00:22:14.600 account finally T offers a referral program where you can earn 10 T dollars 00:22:12.600 --> 00:22:18.159 for you and a friend when they place a successful order with your unique 00:22:16.159 --> 00:22:22.000 referral link order online pop in your Telos Sim and you're done you can even 00:22:20.640 --> 00:22:26.080 keep your phone and number which makes the switch even easier so switch to T 00:22:24.240 --> 00:22:29.200 today by clicking the link in the video description if you enjoyed this video 00:22:27.960 --> 00:22:36.480 you might enjoy the the last time we took a look at a wild SSD carrier card 00:22:31.799 --> 00:22:36.480 the liquid honey badger