 So this is exciting. We are finally going to be validating if our idea for the rendering machine over there is gonna work, but first, we need a long ethernet cable. So... FreshBooks is the online invoicing solution that lets you get organized, save time, and get paid faster. Click on this spot right here for a free trial now. Alright, so one of the few pieces of the puzzle still miss- well, there's a few pieces of the puzzle still missing. Okay, one of the pieces of the puzzle still missing is getting a 10 gigabit ethernet connection to that machine. So we've swapped out to the Super Micro board that doesn't have it on board, but the good news is... Oh, I just dropped one. Okay, well the good news is my X540s and other 10 gigabit cards are here now, so... We're gonna go ahead and get that puppy linked up. Then we have to actually build the machine. I've just had it in a test bench up till now, so... This... this was the thinking behind the carabiners in the ceiling. Okay. So now in theory... We are 10 gigabit. Sick! Alright, we are good. So... Let's- let's actually- let's actually build this machine, finally. Finally! Okay, so I thought that this... RPC-4224 was actually gonna be one for us to grow into, but it looks like... We need it now. So this is the last of my 4U cases from Norco that they graciously provided for our new server room. And we are gonna be using this one for the rendering machine. So there's all of our mounting hardware. There's our nice soft foam that my cat would eat if he could get at it. And he would try to swallow it, and he would then get it stuck in his stomach, which he did again. Costing me another $1,200. If he does it again, I'm gonna kill him. That's twice in four months he's eaten foam and needed surgery. Ugh! So there... It would have been cheaper to get two new cats the first time. Now I could have had three new cats and, like, a pretty cool lizard. Alright. But he's my baby and I love him. That's what I tell myself. It's like, gee, why doesn't Linus have a Lambo with all that YouTube money? Because he has the world's most expensive cat. That's why. Okay. Um, I'm gonna need a minute to clear some space here, I think. Um... And machine gun. Um... Power supply. Now I could leave the 860i that I have in there, but then if I ever want to actually put graphics cards in, because I'm gonna take those graphics cards out, if I ever wanted to put proper graphics cards in, then I would have to replace it with something else, which is kind of a pain in the butt. So... Hmm... You know what? No, I'm gonna stick with the 860i. The odds of throwing graphics cards in here are pretty slim. Do you know how long it's been since I've seen a motherboard where I actually have to pop the covers on the I.O. plate off myself? It's like, are you for real? Yolo, man. Oh, that's really tight. Okay, I need pliers. Okay, just doing a quick test fit here, finding out where the devil all the holes are. So, that one over there and this one right here. What? Okay, so there's that one. There's that one, there's that one. Where's this one? Do you need all of them? Well, it's optimal. I can get away with two, I think. That's what I do. This show is all about the right way to do things, so... So... Is that at least three? I guess we'll need a power supply at some point. Okay. Oh, look at that! There's fan headers over at the front here. It's perfect, it's like Christmas. It's kind of a weak Christmas. A fan header? Your expectations are so high. How did you know that I wasn't going to do fan headers for Christmas bonuses this year? Now my feelings are hurt. They should be. Now that my feelings are hurt, maybe there will be no Christmas bonus. Do you ever think of that? Bet you'd rather have a fan header than nothing. No, I think I'd rather nothing than fan headers, just because that's kind of insulting. Duly noted. Merry Christmas, everyone. Here's poop. Do you like poop? Oh, you want poop? Nothing. I think everyone in the comments will agree with me that fan headers are better than poop. That doesn't even make sense. At least you could use poop. For what? Leaving on your boss's desk for giving you fan headers? For bosses who give you poop. I actually ordered a game with little turds and Velcro helmets that you wear that they stick to on Amazon that I was thinking we'd play on. It was super fun. So it occurs to me now I need a graphics card. I didn't really want to put one in here, but this motherboard has no onboard graphics. And you're sure you can't use a Titan. So I'm thinking as I install the power supply, this is the one piece of hardware in this machine that I would really like to change. Not because the 860 watt isn't enough for what we're going to do. And that may be the case in the future if we find some kind of application that can take advantage of GPU, which is why I wanted a motherboard in the first place that would support multiple GPUs. But the reason I would like to have a different power supply in here is actually more to do with redundancy. But finding a mini-redundant, so that's what they're called, a mini-redundant power supply, one in this form factor, of sufficient wattage for this system with a couple of high-power GPUs, actually not easy. There's a 600 watt. There may be something higher than that. Feel free to leave a message in the comments if you guys can find something better than that. But yeah, I'm pretty much stuck with a single non-redundant power supply. The good news is this is a very reliable power supply, and this machine won't actually be storing anything mission critical. Data goes on to another server, gets ripped off of it, and then transcoded over to another server by this one. It never actually touches the data. So it should be fine. It's just I would rather it was actually redundant. And it'll be on a UPS as well, so the power supply would have to fail to take it down even temporarily. I guess it's all right. All right, in theory this boots now. Anytime. Hey, hey, hey, all right. Okay. So here we are. Here's our 72 CPU threads, only half of which are actual cores. Weak sauce, I know. And this, my friends, is the reason for some of the confusion around this particular system. Had a lot of people asking things like, why do you need so many CPU cores? To which I replied, nothing, because I wasn't really ready to talk about what the solution was yet. The reason we need so many CPU cores is we're going to be using it for transcoding and then doing the final outputs of our videos to make our videos easier to work on on our workstations without lag as we're scrubbing through the timeline and to make our exports more seamless of the finished videos and hopefully faster. Question number two, Linus, why aren't you running Linux on a server? It's a server. To which my reply is, well, gee, I guess if you'd maybe asked what software we were using, I might have been able to reply that the software we're using doesn't run on Linux. And in fact, there isn't a Linux version. So we're going to be using Sorensen Squeeze Server. And how this works is pretty much it's... It's not server. This isn't server? Well, where's server? We are going to be using Sorensen Squeeze Server. And the way that works is we pretty much have a watch folder that we drop files into and it transcodes them for us. So we had to do a fair bit of experimentation by we, I mean Ed, who's behind the camera, had to do a fair bit of experimentation to find out exactly how much we could get out of our 36 CPU cores. And if we did, would it even do anything positive for our workflow? So the exact workflow is not 100% finalized yet. But what we do know is that if we use encode and watch folders, and we set ourselves up a watch folder and a destination, when we ingest footage off of our cards, which will be over Thunderbolt, so we'll actually be able to ingest very quickly, even off multiple cards, automatically our watch folder is going to take those and apply a particular preset to them. So we can take a big whack of footage, which we've actually got on the local disk here, and then we are going to copy here. And this will do two things. So number one, it will take the footage off of our SD cards, which we would cut paste instead of copy pasting. And then number two, now that it's safely on our storage array, it will take these and transcode them to a different, easier to work with format, and then boot them out somewhere else. So in this case, we are using another local folder, which, oops, I just paused that, which may end up being a bottleneck, but we'll do a quick experiment before this video is over to find out if our 10 gigabit network is going to benefit us here. What we're waiting for now as the files copy is we've set up our watch folder to monitor itself every one minute, and then start processing so we can have a look at our current jobs. Nothing has happened yet, but we'll know soon enough because our CPU is going to start going bananas here. Oh, here we go, here we go. I think something's happening. 5%, 7% CPU. Let's see if the job is showing up. Yep, there we go. So you can see it's taking all of these clips and importing them, then transcoding them, then it does something else. And there's a lot of waiting involved. But our CPU usage should start to slowly ramp up as more of them get past the importing stage and make it to the encoding stage. Excuse me, transcoding, which I guess is also encoding. 76. Oh, it's going up to 85%. Oh, now it's working. Well, what the Sam heck? I guess it just takes a while to get all fired up or something. Look at it go. We're actually getting a fairly reasonable turbo frequency out of this whole process, like 2.7 plus gigahertz right now. So there's actually a couple of different views we can get of this. It looks like CPU zero is getting most of the love, but we can actually change it to look at the two different NUMA nodes. And you can see that CPU zero's utilization is higher, but it's not that much. Well, it is quite a bit higher. So it is significantly higher than node one. And then we can also change the graph to overall utilization. So you can see as it climbs really high, CPU one kind of catches up to zero, but it is significantly lower. None of these jobs are finished. They're all at the importing or transcoding stage still. He's very interesting. Okay, so we're only seeing like max highest peak, 70% CPU utilization. And we realize that the last time we validated any of this, it was actually in this server with one of the processors plugged into the motherboard. So maybe the advantage that this one has over the one we're using now is much, much faster storage. So if we can connect to this one over the network, then we should be able to leverage that storage in theory. So let's fire up the 24 SSD server and see if using that as a target helps. One gigabyte per second over the network. And what's interesting about being able to see network utilization here is that unlike local disk utilization, we know where the hard cap is. And it gives us a really clear idea of how much CPU utilization corresponds to how much network utilization. You can see network is actually not even changing in spite of the fact that CPU has gone from 13 to 45%. But what remains to be seen is whether our CPU usage will go higher than it was able to before with less of a storage bottleneck. So like so many of our videos, this one ends up actually raising more questions than it answers. But hopefully we were at least able to answer the question of why we wanted such a high powered server. It's to enable a smoother workflow when multiple people are hitting the files at the same time. And in order to have an easy, quick way to replicate our data as soon as we ingest it onto our server, so we can avoid the current workflow, which is just leave it on the SD card just in case, because there's only one copy on the server. This way, we'll actually have a copy on one server and a copy on another one as soon as we've ingested the footage and it has gone through this transcoding process. Okay, so we're back at the... Ugh. The current office for now. But that doesn't mean I'm not going to take an opportunity to tell you guys about our sponsor today here. And that is H-E-R-E, not H-E-A-R, in spite of the fact that these things go in your ears, is a pretty unique little campaign that's up on Kickstarter right now. Now, to be clear, these are not earbuds. They're not a Bluetooth handset. They're not any of those things. What they are is they're a real-world, real-time sort of audio effects applicator, so you can adjust the volume of the real world. You can change EQ settings of the real world. You can go ahead and, you know, like say, for example, you're at a concert and you're like, you know what this could use? Some reverb. You whip up the app on your phone and if all goes according to plan, you'll be able to add like a concert hall sound to that dude in the cubicle next to you, if you so desire. Or you could do more useful things with it, for example, like tuning out a baby on an airplane or even the engine noise on an airplane, simply by making adjustments through the app. They're quoting a six-hour battery life and it comes with a charging case that holds an additional two charges. So over the course of your day, I'm sure you'll come up with a lot of interesting effects application things to do to it. Now you might be asking yourself, okay, well, hold on a second. What about the latency? They're quoting 30 microseconds between the microphone on the outside and the speaker on the inside, taking noises, changing them, and then blasting them into your, it doesn't have to be blasting, there's a volume control, and then blasting them into your ears for you to hear. So if you're curious to learn more or you want to support them, check out the Kickstarter page, which is linked in the video description. Thanks for coming along for the ride, you guys. If you disliked the video, I think you know what to do, but if you liked it, then go ahead and press that like button, it helps us out a lot, and get subscribed and all that good stuff. If you really liked it, then you can go ahead and check out the links in the video description, where you can buy a t-shirt, give us a monthly contribution, or change your Amazon bookmark to one with our affiliate code, that helps us out a lot. And I guess that's pretty much it. Thanks again for watching, and if you are looking for something else to watch after having done all that stuff, then go ahead and click the little I in the top right corner and check out the video on channel. Super fun that we did where a certain Taryn Van Heemert and an electrical vehicle and some thug life involved. I don't think that's how you hold it. You should probably have clothes. Yeah, there you go. I don't know what I'm doing.