WEBVTT 00:00:00.320 --> 00:00:08.080 Technology has always been a huge part of my life, but my other secret passion 00:00:05.359 --> 00:00:12.639 is badminton, a fast-paced technical racket sport. And after years of 00:00:10.400 --> 00:00:18.320 searching, I finally found the perfect property to satisfy my craving for both. 00:00:15.920 --> 00:00:23.439 By day, it's Smash Champs, a state-of-the-art badminton club. But 00:00:20.240 --> 00:00:25.279 just beneath the surface lurks a secret. 00:00:23.439 --> 00:00:31.679 Because if you look closely, you'll see we invested tens of thousands of dollars 00:00:28.480 --> 00:00:34.079 into making this the ultimate esports 00:00:31.679 --> 00:00:38.559 land gaming venue. I'm talking stupid fast fiber optic networking, on-site 00:00:36.320 --> 00:00:43.200 dedicated servers for any game you can imagine, and a crapload of power. And 00:00:41.520 --> 00:00:49.200 with the city of Siri's blessing, we're going to be bringing together over 200 00:00:45.600 --> 00:00:50.719 gamers for what we call Whale Land. Woo! 00:00:49.200 --> 00:00:55.520 We are getting so close to the first event here, guys. But there's one small 00:00:52.960 --> 00:00:59.280 giant problem. While the occasional badminton player might watch a YouTube 00:00:57.440 --> 00:01:03.039 video on their phone now and then, we haven't stress tested any of the 00:01:01.520 --> 00:01:07.280 infrastructure that we installed over the last couple of years. That means we 00:01:05.199 --> 00:01:12.320 have no idea how everything's going to hold up under heavy use. So, I recruited 00:01:10.080 --> 00:01:17.360 a few dozen of my closest paid friends to come together for the ultimate stress 00:01:14.880 --> 00:01:23.040 test, an overnight caffeinefueled weekend gaming session. And it starts in 00:01:20.159 --> 00:01:23.040 6 hours. 00:01:31.600 --> 00:01:39.200 Guess what? It's Lime Day. This week on ltstore.com, we are squeezing the heck 00:01:36.720 --> 00:01:44.799 out of our margins to bring you some really sweet deals. 00:01:42.159 --> 00:01:50.880 Today only, get a stretchy and comfy sport button-up for 50% off. Or snag a 00:01:48.079 --> 00:01:56.479 fun and colorful Macadress Oxford for 75% off while supplies last. Save $20 on 00:01:54.320 --> 00:02:01.119 a mystery screwdriver and get one of five exclusive Lime Day colorways. Pick 00:01:58.880 --> 00:02:07.119 up a commuter backpack and you'll get either an 8bit do controller with a 00:02:03.360 --> 00:02:09.840 charging dock or an LTX Ridge wallet for 00:02:07.119 --> 00:02:15.760 free. And best of all, you get free shipping on every order over $175 00:02:13.599 --> 00:02:20.640 if you're shopping from the US and every order over $250 Canadian if you're 00:02:18.560 --> 00:02:26.239 shopping from anywhere else. So, don't wait. Visit LMG.gg/lime 00:02:23.920 --> 00:02:30.160 before it's too late. No, I'm not doing that again. Thankfully, there's not that 00:02:28.160 --> 00:02:32.959 much to do. We just have to unload the truck, build all the cable harnesses, 00:02:31.440 --> 00:02:36.800 set up all the tables. Not to mention this server, which is brought to you by 00:02:34.640 --> 00:02:42.160 our sponsor, Kioxia, who sent over some of their top-of-the-line CM7 Gen 5 NVMe 00:02:39.840 --> 00:02:47.120 SSDs that are going to be powering the fastest Steam cache that we have ever 00:02:44.800 --> 00:02:53.519 shown you guys. See, the thing is, we've only got 3 GB internet here, which is a 00:02:50.319 --> 00:02:55.680 lot even for 200 people. But as we've 00:02:53.519 --> 00:03:00.560 observed in the past, the biggest source of traffic at lands tends to be things 00:02:57.680 --> 00:03:05.280 like updates. So, if Microsoft decided to push a big patch or if Deadlock 00:03:02.959 --> 00:03:09.840 updated for the third time that week, then everything else could slow to a 00:03:07.360 --> 00:03:14.159 crawl. That is where our caching server comes in. In simple terms, it's a 00:03:12.080 --> 00:03:18.159 computer that sits in between our internet connection and all of our 00:03:15.920 --> 00:03:22.239 attendees so that rather than our internet maxing out and lagging 00:03:20.080 --> 00:03:26.480 everyone's games, the update will get saved to the cache the first time it 00:03:24.239 --> 00:03:30.799 gets downloaded. And then when every other person goes to grab that same 00:03:28.640 --> 00:03:35.040 update, hey, we already have the files stored and we can serve them from our 00:03:33.040 --> 00:03:39.040 cache, saving our precious internet bandwidth. And all of that happens 00:03:36.799 --> 00:03:42.799 entirely transparently to the user. Meaning, unless they're a network nerd, 00:03:41.599 --> 00:03:48.879 they can't even tell that it's happening, aside from their update downloading super fast, of course. 00:03:45.760 --> 00:03:52.640 And by super fast, I mean super fast. 00:03:48.879 --> 00:03:55.519 Thanks to the these four Kioxia CM7 PCIe 00:03:52.640 --> 00:04:02.480 Gen 5 enterprise SSDs at the heart of our caching server. Each of these 15.36 00:03:58.480 --> 00:04:04.720 TB SSDs can do, and I kid you not, 14 GB 00:04:02.480 --> 00:04:10.319 per second read speed and an astonishing 2.4 million 4K random readiops. They're 00:04:07.760 --> 00:04:14.879 available in both E3. S and U.2 form factors like we have here. And they or 00:04:12.799 --> 00:04:18.320 any other SSD from Kopia's phenomenal lineup is a great choice for your next 00:04:16.479 --> 00:04:22.560 server project, big or small. You can check them out at the link in the description and we'll also have links to 00:04:20.799 --> 00:04:25.520 the rest of the parts we're using. Speaking of other parts, um, what do we 00:04:24.960 --> 00:04:30.160 got here? Uh, how about the case? Sure. 00:04:28.479 --> 00:04:34.080 Okay, thank you for that. Oh god. 00:04:34.080 --> 00:04:40.560 Right on the motherboard side. 00:04:37.440 --> 00:04:43.360 This is the Silverstone RM23502 00:04:40.560 --> 00:04:47.919 Mini. It's not the fanciest rack mount case ever, but it's nice and compact, 00:04:45.440 --> 00:04:52.800 relatively inexpensive. They sell a rail kit for it. And more importantly, it has 00:04:50.400 --> 00:04:55.520 5 and a/4 in bays up front. A perfect spot to put our 00:04:53.919 --> 00:05:01.040 optical drive. Nope. There wasn't a ready-made solution for 00:04:57.919 --> 00:05:03.520 this. Nobody really makes a Gen 5 ready 00:05:01.040 --> 00:05:08.320 5 and a/4 in U.2 bay. So, well, actually, Icy Do has one on their 00:05:06.240 --> 00:05:11.360 website under concept projects. Oh, okay. They have like mockups and everything. I 00:05:10.560 --> 00:05:16.720 just don't know if they've ever made one. And I didn't respond to the email. So, Jake designed our own. Yeah, it's 00:05:15.120 --> 00:05:20.000 basically the same thing, just crappier and 3D printed. Okay. 00:05:18.320 --> 00:05:25.680 But it works well. And these are just Gen 5 uh U.2 to MCIO cables. So, other 00:05:24.320 --> 00:05:28.880 than that, it's just kind of a plastic holder. Builds its purpose. 00:05:27.440 --> 00:05:32.479 And you printed this on the new Prusso, right? Yeah. Well, it's not really that new Prussa XL. 00:05:31.440 --> 00:05:37.680 Looks nice though. Hey. Yeah. Oh, I love this carbon fiber reinforced filament. 00:05:35.360 --> 00:05:39.680 Yeah. And uh it shouldn't melt. Shouldn't. 00:05:38.400 --> 00:05:44.639 Exactly. Does it have any cooling? Uh it will. That's what that is. So it 00:05:42.639 --> 00:05:48.800 just kind of goes like kind of like this with the cable 00:05:46.720 --> 00:05:52.400 and it goes like that. And then we have one 40 mm knock to a fan. 00:05:51.039 --> 00:05:54.880 Mhm. I have a couple more in just in case. 00:05:54.400 --> 00:05:59.360 Okay. But um I'm kind of hoping it's maybe okay. 00:05:57.520 --> 00:06:04.319 Okay. I guess now's a good time to talk about the motherboard that limits us in 00:06:01.280 --> 00:06:05.840 that way. This is the ASRock Rack Epic 00:06:04.319 --> 00:06:10.639 4000D4U. It's MATX, which fits perfectly in our 00:06:08.160 --> 00:06:15.840 case. It has remote management, which it darn well should being a server. And 00:06:13.199 --> 00:06:22.000 perhaps most importantly, it's got these 2x8 MCIO connectors, which are perfect 00:06:18.639 --> 00:06:24.160 for our four Kioxia SSDs at full Gen 5 00:06:22.000 --> 00:06:29.280 speeds. It's also compatible with the CPU that we're using, which 00:06:26.960 --> 00:06:34.160 in spite of the name of the board, is not an Epic. Instead, we've gone with 00:06:31.360 --> 00:06:40.160 AMD's latest and greatest desktop CPU, the Ryzen 9 9950 X3D. As for why we made 00:06:38.240 --> 00:06:44.240 this choice, well, a number of reasons. Starting with the fact that it's a lot 00:06:42.000 --> 00:06:49.039 less expensive than many of the full fat epic alternatives. And with the amounts 00:06:46.479 --> 00:06:52.560 of PCIe Gen 5 lanes and the memory bandwidth they have on these top-end 00:06:50.560 --> 00:06:58.080 desktop chips these days, it's a surprisingly viable option. And that 3D 00:06:55.520 --> 00:07:03.919 vcache does help it perform better in caching workloads like this. I couldn't 00:07:01.039 --> 00:07:07.280 help noticing that our cooler though. Is this really going to work for a 00:07:05.840 --> 00:07:14.560 9950X3D? We're going to find out. The cool thing about AMD chips is even 00:07:11.680 --> 00:07:18.080 with the power super limited, they still rip. And AMD has like an eco mode 00:07:16.800 --> 00:07:21.919 functionality that limits it to a certain TDP if we have to. But I'm thinking we can just try undervolting 00:07:20.800 --> 00:07:27.520 and seeing what happens. Okay. I mean, realistically, we didn't choose this because we like doing any of 00:07:25.919 --> 00:07:31.759 that. It more comes down to the fact that in a 2U form factor, 00:07:30.080 --> 00:07:34.800 there aren't really a lot of other options. Lionus decided he had a meeting 00:07:33.520 --> 00:07:39.520 to attend. So, I've been trying to get the SSD holder thing assembled. I 00:07:37.599 --> 00:07:42.479 realized that I kind of flubbed up a little bit and didn't make space for the 00:07:41.440 --> 00:07:49.199 connectors on the back. So, I trimmed that with some snips, screwed in our cables, and in theory, this can now 00:07:46.319 --> 00:07:53.520 mount in the bay. I say in theory because haven't tried. Oh, it looks like 00:07:52.000 --> 00:07:58.960 the holes mostly line up. That's a good sign. While Ryzen 9000 desktop chips do 00:07:56.319 --> 00:08:03.680 support ECC, I uh couldn't help noticing that we very much did not do that thing. 00:08:02.000 --> 00:08:08.240 Well, look how cool this RAM is. And it's worth addressing that while yes, 00:08:05.680 --> 00:08:11.840 you can run ECC memory on supported motherboards with Ryzen CPUs that 00:08:10.560 --> 00:08:14.319 there's still some weirdness with certain boards, and I just didn't want 00:08:13.680 --> 00:08:21.599 to deal with that. Uh, speaking of weirdness, I couldn't help noticing that this case uses just 00:08:19.039 --> 00:08:25.599 like a standard ATX power supply. Yeah, this this would work great in a rack. 00:08:24.080 --> 00:08:28.160 See? See all that air flow? That would definitely be there if you had a switch 00:08:27.120 --> 00:08:35.760 or something on top. Yeah. So, how are we planning to get any air flow to our power supply? The FSP 00:08:32.320 --> 00:08:38.240 Twins Pro. It's a a dual redundant power 00:08:35.760 --> 00:08:41.599 supply, but in an ATX form factor. Nice. Okay. So, we don't need a big 00:08:39.839 --> 00:08:45.279 intake here is what he's trying to say. Yeah. This just makes sense. 00:08:43.200 --> 00:08:48.080 What doesn't make as much sense is our boot SSDs. They're made of plastic, 00:08:47.760 --> 00:08:51.839 Jake. I guess so. a couple Patriot Burst Elite 00:08:50.800 --> 00:08:58.240 480 gigs. Yeah, they're they're nothing special, but at least they're redundant, I guess. 00:08:56.080 --> 00:09:01.600 Not really. We'll talk about that later. But our network connection is this 00:09:00.080 --> 00:09:06.640 NVIDIA/Mlanox Connect X6 25 gig dualport nick is 00:09:05.040 --> 00:09:09.120 perfect. It'll give us failover in the event that one of our cables or ports 00:09:08.720 --> 00:09:14.560 barks. Okay, cool. But 25 gig though, I mean, that seems kind of pinner for a cache of 00:09:12.640 --> 00:09:20.480 this magnitude. Well, this wasn't exactly my first 00:09:17.200 --> 00:09:23.440 choice. I wanted to run this a dual port 00:09:20.480 --> 00:09:26.800 connect x600 gig nick instead so we could really push those well I mean to 00:09:24.959 --> 00:09:29.839 be clear not really push those SSDs but push them a little bit. In fact I even 00:09:28.240 --> 00:09:35.920 had Sean and the boys swap out the normal UniFi aggregation switch with 00:09:31.920 --> 00:09:37.519 their like 48 port 25 gig/und gig 00:09:35.920 --> 00:09:42.399 enterprise campus switch. Okay well that's cool. So why aren't we 00:09:38.959 --> 00:09:44.000 using it? However, this motherboard you 00:09:42.399 --> 00:09:48.480 see right here, my friend, while it does make use of all of the PCIe on this 00:09:46.160 --> 00:09:52.800 chip, it shares half of the 16x lanes from this slot with the MCIO port right 00:09:50.720 --> 00:09:55.920 here, which we need for our SSDs. There is a setting in the BIOS to change that. 00:09:54.560 --> 00:09:59.519 Yeah. Where you could just bifrocate it, right? Yeah. We we really just want to use 00:09:57.760 --> 00:10:03.680 eight lanes for the nick. But if there's any card in here that has all 16 lanes, 00:10:02.000 --> 00:10:07.279 it just ignores the setting and doesn't work. However, if you have an 8x slot in 00:10:05.680 --> 00:10:12.800 here, this doesn't work until you set that setting. So clearly it does something. 00:10:09.519 --> 00:10:14.640 Okay. So what we could do maybe is just 00:10:12.800 --> 00:10:18.640 put nail polish on. I was thinking Dremel, 00:10:16.560 --> 00:10:20.880 but then that seemed pretty bad. So captain tape. It's like micro electrical 00:10:20.560 --> 00:10:28.320 tape. So we just need to cover up exactly by eight of the lanes. That should give 00:10:24.880 --> 00:10:30.000 us about 16 GB a second. And that's more 00:10:28.320 --> 00:10:33.519 than double what we'd be able to do with that dinkier 25 gig card. 00:10:31.760 --> 00:10:41.139 Which is like 6 GB a second. Yeah. We have a lot more to do before that goes in though. 00:10:42.480 --> 00:10:51.200 All right, let's get this 5 and a/4 inch bay thing in here. Uh oh boy. 00:10:47.600 --> 00:10:52.480 Uh-oh. Uh-oh. Okay, this might actually 00:10:51.200 --> 00:10:57.440 No, she's in. She's in. Don't worry. There's extra room. I have an idea. I am 00:10:55.120 --> 00:10:59.040 taking off these screws. Those are the wrong screws. 00:10:58.399 --> 00:11:03.440 Don't worry about it. You want these ones? Don't worry about it. See, I'm just going to disassemble some more 00:11:02.800 --> 00:11:07.680 of the case. But for why? For why? Everything is fine. For whence? 00:11:06.720 --> 00:11:10.959 For to Why don't you just slide it in from this side? 00:11:09.839 --> 00:11:16.399 Cuz it won't. Why? Unless I do this. No, that won't go. 00:11:14.240 --> 00:11:21.120 Okay, there we go. Oh, that's the problem. 00:11:18.399 --> 00:11:24.399 These little ears on this piece don't sit on the front. They go in from the 00:11:22.959 --> 00:11:28.880 back. I didn't need to take any of that out. What happened? Don't worry about it. Everything's good. 00:11:28.160 --> 00:11:32.880 Everything's great. Wow, that looks great. Does look great. I put little threaded 00:11:31.680 --> 00:11:37.839 holes so that we could have a little screw that went in and kind of like friction held these in. Yeah, 00:11:36.160 --> 00:11:40.959 they're kind of just like in there good enough. This is really tight, dude. 00:11:39.839 --> 00:11:44.320 What? What are we talking about? This right here. Oh, it's tight. 00:11:43.440 --> 00:11:52.079 Damn. It's tight as a tiger. What? So, what time is it, by the way? 00:11:48.800 --> 00:11:54.240 Oh my gosh, it's almost 4. 00:11:52.079 --> 00:11:58.320 I have Wancho in 45 minutes at the studio. Okay, let's be real. You don't actually 00:11:55.760 --> 00:12:02.480 do Wancho at 4:30. Literally no air flow for this RAM. But who needs it, right? 00:12:01.040 --> 00:12:05.200 Wait, did you not add the fans? What fans? You have to add fans to the case, you 00:12:04.880 --> 00:12:10.000 door. What fans? The fans on the table. 00:12:08.000 --> 00:12:12.959 Well, where the heck am I in the front there? There's two fan mounts there, bud. 00:12:11.760 --> 00:12:18.160 Dude, there's no room. Yes, there is. There is exactly 25 mm. 00:12:16.320 --> 00:12:22.399 He's over here playing with Falcon Northwest gaming computers. 00:12:20.800 --> 00:12:26.320 Oh, that looks really cool. It does look cool. Kelt it up like a 00:12:24.079 --> 00:12:30.880 special one for me to game at the land today with. It got a little bonked in shipping and 00:12:28.959 --> 00:12:34.079 one of the fans was like scratching against something. So, we had to take 00:12:32.240 --> 00:12:37.600 the fan out and receat it. But now it's good. And I'm just putting the cable 00:12:36.160 --> 00:12:43.440 management back to where it was. Like, look at this. Look at how anal they are. 00:12:40.000 --> 00:12:45.360 That is mint. Do we only have three fan 00:12:43.440 --> 00:12:49.600 screws? This is why I hate doing builds outside of the studio. Okay, I'm done my 00:12:47.519 --> 00:12:53.279 part of the job. Where are you at? Just don't start saying numbers. 00:12:51.760 --> 00:12:57.120 numbers. 236 75. 00:12:55.440 --> 00:13:01.120 Dude, I'm ADHD enough that that would actually trip me up. Okay, mark the thing. 00:12:58.880 --> 00:13:05.839 My god. Well, you keep saying 38. Oh, you wrote it down. 00:13:04.320 --> 00:13:08.720 Man knows himself. Honestly, I think there's there's definitely worse ways we could have done 00:13:08.480 --> 00:13:16.240 this. Oh, yeah. 100%. Mint. 100%. Okay, here we go. 00:13:13.360 --> 00:13:18.959 Snickers. Yo, this might be too nice for us. Wait, 00:13:17.760 --> 00:13:22.000 wait, wait, whoa, whoa, whoa. You're breaking the law. 00:13:21.360 --> 00:13:27.040 Don't do it. You're not wrong. Don't do it. We don't need the bad GB's today. Oh 00:13:24.880 --> 00:13:30.079 god. No, we don't. We literally don't have time for bad GB's. 00:13:28.560 --> 00:13:32.000 Okay. Do we have a monitor? No, we have IPMI. 00:13:31.600 --> 00:13:35.360 Oh, we have a remote management interface. Are we just going to take this straight 00:13:34.639 --> 00:13:39.839 up to the rack? Kevin's looking at me. You see him? Look at him. He's looking at me like that 00:13:38.079 --> 00:13:43.440 because he gave me a monitor. But I don't need your stinking American 00:13:41.839 --> 00:13:46.800 monitor. Elbows up, baby. Oh my god. Stop. 00:13:45.760 --> 00:13:51.200 Oh god, that's awesome. I need another power cable. No, you don't. Here, I'll solve that for 00:13:49.519 --> 00:13:54.959 you. Ah, fixed. That CPU fan really goes, eh? 00:13:52.959 --> 00:13:58.560 It's because the IPMI is not moving up yet. 00:13:56.639 --> 00:14:02.560 Oh, I was like, why can't I feel any air from the fan that goes down there? 00:13:59.920 --> 00:14:04.639 Yeah, it's impossible. Stick your finger in the hole. 00:14:02.959 --> 00:14:08.800 No, I don't need Do it. Just do it. Stick it. Stick it. You feel it? 00:14:06.560 --> 00:14:12.800 Yeah. You didn't even You did his finger did not penetrate. I just want the cable management done. 00:14:11.199 --> 00:14:16.959 While Jake sets up that server, why don't I talk layout with Chase? 00:14:14.880 --> 00:14:20.560 This is only a a network and infrastructure test right now. So, we're 00:14:18.639 --> 00:14:24.240 only expecting about 50 to 60 people to show up. So, it's not the entire land, 00:14:22.240 --> 00:14:28.160 but that's plenty for us to stress test the physical elements, like our floor 00:14:26.320 --> 00:14:31.920 protectors, for example, which this is my first time actually seeing. It's from 00:14:30.160 --> 00:14:35.519 Facility Armor. It seems like they did a great job. These just go down. They've 00:14:34.000 --> 00:14:40.240 got these Velcro strips that hold everything in place and seems like it 00:14:37.360 --> 00:14:44.079 won't be damaged. Now, one of the main things because this is a badminton 00:14:42.079 --> 00:14:49.279 center first and foremost is that we need to be able to roll in and roll out 00:14:46.880 --> 00:14:54.320 as fast as possible. So, we've got a pretty cool plan for how to handle our 00:14:51.680 --> 00:14:58.639 cabling. Instead of distributing hundreds of Ethernet cables to each 00:14:55.920 --> 00:15:03.600 attendee to plug in, we've made these power and Ethernet whips that will just 00:15:01.360 --> 00:15:07.040 be rolled out as part of our setup. We measure the length of our cables using 00:15:05.040 --> 00:15:11.920 our schematics. Then we had Infinite Cables make a whole bunch of custom 00:15:09.120 --> 00:15:16.720 length Cat 6A Ethernet cables and threeprong extension power cords. Huge 00:15:14.959 --> 00:15:20.480 shout out to those guys. Again, it really does seem like their supply of 00:15:18.240 --> 00:15:24.480 cables is infinite. We'll link some of their stuff in the video description cuz 00:15:21.920 --> 00:15:30.639 they provided literally all the cabling for the entire facility, including 00:15:27.839 --> 00:15:36.880 the fiber. More on that in a sec. Then all of the cables run back to these. On 00:15:33.920 --> 00:15:42.800 the bottom, we've got these sick 50 amp 28vt power distribution units. And then 00:15:39.760 --> 00:15:44.720 we use this Chungus California standard 00:15:42.800 --> 00:15:50.399 power connector that's pretty standard in event spaces. And then on top of 00:15:47.519 --> 00:15:54.720 them, we actually bolted our network switches. Each of our rows gets one of 00:15:52.399 --> 00:15:59.920 these Ubiquiti Enterprise 48 PoE switches. These are the same ones that 00:15:56.480 --> 00:16:02.160 we used back at Whale at LTX in 2023. 00:15:59.920 --> 00:16:08.240 RIP LTX. I still can't believe they sent all of these anyway because they did. 00:16:05.600 --> 00:16:11.920 Each seat will get at least a two and a half gig connection. And who knows, 00:16:09.920 --> 00:16:18.079 maybe we could bump it up to 10 gig for the VIPs or the whales. Each row gets 00:16:15.759 --> 00:16:23.360 two 10 gig single mode fiber uplinks into those switches for a total of 20 GB 00:16:20.720 --> 00:16:27.440 aggregate. And then you can actually see all the power connections spaced out 00:16:25.120 --> 00:16:32.320 along here. Once we're ready to do a real event, this entire space will be 00:16:30.399 --> 00:16:35.759 filled with desks and chairs. Okay, we got the system booted up here, 00:16:33.920 --> 00:16:39.279 plugged into our network switches for one of the rows just for now. I want to 00:16:37.759 --> 00:16:43.440 make sure everything's working before we actually install it in the rack. And it 00:16:41.440 --> 00:16:47.680 does look like the network card is running at PCIe Gen 4 by8, which is 00:16:46.000 --> 00:16:53.279 great. We taped off the extra pins, and that happens to have worked. However, I 00:16:50.639 --> 00:16:56.399 only see two of the four SSDs we have installed, which means the BIOS setting 00:16:54.880 --> 00:17:02.160 I talked about earlier is not set. Moment of truth. I'm in the BIOS. 00:17:00.160 --> 00:17:05.760 Sick. Okay, it is set to the wrong setting. I know that's weird to be like 00:17:03.920 --> 00:17:10.720 excited about something being wrong. Hit save and let's see if it works. Fingers 00:17:09.280 --> 00:17:15.839 crossed. Oh, actually, I should mention this thing. It's uh one of Eaton's new 00:17:12.640 --> 00:17:17.360 trip light cloud connected UPS's. Um, 00:17:15.839 --> 00:17:20.720 I'm running the cache off it right now because we were kind of screwing around 00:17:19.280 --> 00:17:25.839 with the power situation during the setup. And these are pretty sweet because rather than having like a 00:17:23.679 --> 00:17:29.360 management weird thing that runs off of them, you just plug it into the internet 00:17:27.360 --> 00:17:34.559 and adopt it to their cloud software and you can monitor and control these UPS's 00:17:31.840 --> 00:17:37.200 and they're like small, compact, and not crazy expensive. We'll have links to 00:17:35.919 --> 00:17:41.120 those down in the description along with all the other parts like the bits for 00:17:39.039 --> 00:17:45.120 our computers and our Kio SSDs down there. Got back into the BIOS and the 00:17:42.960 --> 00:17:49.760 SSDs are all there. Our network card is all there. The system works, baby. Now 00:17:47.600 --> 00:17:53.520 we just have to put it in the rack, do all the software setup, and there's 00:17:51.280 --> 00:17:58.320 already people here. It's now I don't have a watch. It's 7:00 p.m. We're late. 00:17:56.480 --> 00:18:01.760 There we go. Perfect. I know we said earlier we were going to mount this on 00:17:59.600 --> 00:18:06.559 rails, but the rails that come in the rail kit look awful. And uh it just has 00:18:05.200 --> 00:18:11.039 this nice spot where it can sit right here and be future Sean's problem. Screw 00:18:09.120 --> 00:18:15.840 that guy. Look at that. We got both of our 100 gig links in an aggregate. We're 00:18:13.679 --> 00:18:19.919 ready to go once we set it up. Except I was smart 00:18:18.320 --> 00:18:23.600 enough to already have done that at the office. And here's how you do it with 00:18:21.760 --> 00:18:28.960 two really cool pieces of software. First, LANC cache. That's the heart of 00:18:25.919 --> 00:18:31.280 how this whole operation works. It takes 00:18:28.960 --> 00:18:35.919 the incoming data stream, which is like your Steam game downloads, stores them 00:18:33.600 --> 00:18:39.520 on the storage locally so that the next time you download something, it gets 00:18:37.679 --> 00:18:43.120 pulled from the cache instead of the internet, which is what saves us 00:18:40.720 --> 00:18:47.360 bandwidth. and then the operating system called flat car container Linux. Now, 00:18:45.520 --> 00:18:51.760 because LANC cache runs in a Docker container, which is kind of like a mini 00:18:49.520 --> 00:18:55.919 operating system that runs within your main operating system, and it's the only 00:18:54.240 --> 00:19:00.080 thing we're going to really be running, we don't want the main operating system 00:18:57.760 --> 00:19:03.440 to be like this big cludgy mess like Windows that needs updates all the time. 00:19:01.919 --> 00:19:08.480 So, we're going to be using flat car container Linux, which is specifically 00:19:05.520 --> 00:19:12.640 built to be as simple and minimal as possible just for running containers. 00:19:10.880 --> 00:19:17.039 And what's really cool about flat car, the main reason that we're using it is 00:19:14.799 --> 00:19:21.840 because the entire setup gets distilled down into a text file. That's how you 00:19:19.360 --> 00:19:26.160 configure LANC cache. We've got our four Kioxia SSDs are going to be in RAID 00:19:23.679 --> 00:19:29.520 zero. All of that good stuff. And then you install it to the computer. And the 00:19:27.760 --> 00:19:33.760 text file tells it how to set everything up. So if you have a boot drive die or 00:19:31.679 --> 00:19:38.559 you have a a new server or or whatever it is, you just reinstall it with a text 00:19:36.559 --> 00:19:42.960 file and it resets it up. It's perfectly repeatable. It's super easy to maintain 00:19:40.799 --> 00:19:45.600 and it automatically updates which is a really good thing for us. We're not 00:19:44.080 --> 00:19:49.840 going to be running these events all the time and um having to worry about that 00:19:47.760 --> 00:19:53.039 sort of stuff. Not something I want to deal with. Now, this is a pretty 00:19:51.120 --> 00:19:57.039 advanced way to set this up, but if you're curious, we're going to post a 00:19:54.880 --> 00:20:00.559 simplified version of this flat car configuration in the video description 00:19:59.039 --> 00:20:05.360 so you can play around with it yourself. Uh it's also the same thing we used for the DIYVPN video. That was pretty fun 00:20:04.080 --> 00:20:10.559 and it worked pretty good. It's just that this time we're installing to our own physical hardware and not through a 00:20:08.720 --> 00:20:15.360 cloud provider. So for this time we're going to use the more old school manual 00:20:13.440 --> 00:20:20.240 install tool. It's literally called flat car-install. So download that and 00:20:17.600 --> 00:20:24.320 install any missing dependencies in the current version of Ubuntu server. We 00:20:22.400 --> 00:20:29.200 just needed bzzip 2. So pseudoapp install bzzip 2. Once you have that, you 00:20:26.799 --> 00:20:32.720 have to download your flat car config file but the system readable version. 00:20:31.440 --> 00:20:37.360 And if you don't know how to make that, check the description. and we'll have some instructions on how to do that. 00:20:35.280 --> 00:20:41.679 Make flat car install executable, figure out what drive you're installing to. 00:20:38.799 --> 00:20:45.440 Ours is dev/ sda and then run the command. It's going to download the flat 00:20:43.520 --> 00:20:48.400 car image, do all the installing, and then throw your config into it. And once 00:20:47.520 --> 00:20:52.960 it's done, you should be able to take your USB out, reboot your server, and 00:20:50.880 --> 00:20:57.520 you'll have a setup LANC cache. Cool tutorial, Jake. Now, let's see how 00:20:55.200 --> 00:21:02.000 it worked, cuz our network test is in full swing. We'll start with a look at 00:20:59.039 --> 00:21:06.000 my setup. My poolcooled computer's a little tough to move, but thankfully 00:21:03.840 --> 00:21:10.159 Falcon Northwest just sent over this frag box for us to check out 00:21:07.440 --> 00:21:14.240 editorially. And I was like, "Oh, good timing, boys. I guess I'll use this for 00:21:12.000 --> 00:21:18.240 the land." They actually did a sick custom print on it for us as well. That 00:21:16.240 --> 00:21:28.000 looks amazing. And uh it's running a Ryzen 9 9950X 3D and an RTX 5090 with a 00:21:23.600 --> 00:21:31.280 whopping 96 gigs of DDR5 6000. This is 00:21:28.000 --> 00:21:33.520 as fast as it gets. And it is shockingly 00:21:31.280 --> 00:21:36.960 compact and totable. Of course, that's not going to help us if Jake's network 00:21:34.880 --> 00:21:41.600 cache doesn't work. And she works freaking awesome. Now, the only question 00:21:39.200 --> 00:21:46.080 is what happens if somebody else tries to download a game at the same time. 00:21:42.880 --> 00:21:47.919 Luke, Luke, download a game. Lionus 00:21:46.080 --> 00:21:52.400 wants to battle. So, let's see what kind of download speed you get and if it 00:21:49.360 --> 00:21:56.799 affects mine. 1.8. 00:21:52.400 --> 00:21:59.440 1.9. Okay. But what am I at? Dude 00:21:56.799 --> 00:22:04.640 hasn't moved at all. What are you at? 2.5. So, we are already exceeding our 00:22:02.960 --> 00:22:08.159 total internet connection speed here. That means the caching is absolutely 00:22:06.320 --> 00:22:12.240 working. Now, we just got to have everybody download a game at the same 00:22:09.760 --> 00:22:20.080 time. Think we can coordinate that? Okay. 3 2 1 click download. Go. 00:22:17.520 --> 00:22:24.480 Okay. Let's check this out. 15 GB. Wow, that's pretty sick, actually. The SSDs 00:22:22.320 --> 00:22:29.200 are like, "Sorry, are you like doing something? I I I didn't even notice. Did 00:22:27.440 --> 00:22:32.320 you breathe next to me? This is freaking awesome. 00:22:30.720 --> 00:22:35.440 It doesn't even care, dude. The CPU usage is at 10%. 00:22:33.919 --> 00:22:37.679 How's our internet usage? Do we know that? The inbound, which would be 00:22:37.440 --> 00:22:43.440 Yeah. Well, there'll be some axe there, but realistically about a gig to play. 00:22:41.600 --> 00:22:45.840 So, a couple people managed to find a game that we don't already have cached. 00:22:45.440 --> 00:22:51.200 Yeah, that's freaking awesome. So, it works. Woohoo. 00:22:48.640 --> 00:22:56.559 Hey, great job, Kyia making SSDs that are way way way way way way 00:22:53.679 --> 00:23:00.559 faster than my CPU can decompress. My CPU is at 100%. 00:22:58.000 --> 00:23:03.679 Yeah, it sure is, buddy. That's probably more our bottleneck right now than the 00:23:02.559 --> 00:23:09.679 actual caching server. Oh, 100%. In conclusion, even though this test was 00:23:06.320 --> 00:23:11.919 only with 40 or 50 people once we expand 00:23:09.679 --> 00:23:14.799 to the entire facility, we've got plenty of headroom left over. If you guys 00:23:13.760 --> 00:23:19.440 enjoyed this one, why don't you check out the time I roasted people's PCs at 00:23:17.120 --> 00:23:25.280 Whale Land back in 2023. Editor note, put this in. 00:23:23.120 --> 00:23:25.280 Thank