WEBVTT 00:00:00.280 --> 00:00:07.399 so it was from the observation that when you tighten an LGA retention bracket 00:00:05.839 --> 00:00:13.240 you'll have to look closely to see it though there's actually a lot of 00:00:10.000 --> 00:00:15.360 pressure on the CPU and it moves 00:00:13.240 --> 00:00:20.080 significantly as you lower the retention arms so I figured you know we're 00:00:17.840 --> 00:00:24.680 probably just not applying enough pressure if we'd found a way to tighten 00:00:21.960 --> 00:00:30.000 the heat sink down enough I think we could have pulled it 00:00:26.119 --> 00:00:33.480 off but we didn't do that so now we need 00:00:30.000 --> 00:00:33.480 need a new way to mount our 00:00:40.440 --> 00:00:45.399 coolers Kingston cascy 310 series ssds 00:00:43.800 --> 00:00:50.199 feature firmware based power loss protection massive capacities up to 960 00:00:48.160 --> 00:00:54.559 gigs and not to mention they perform well enough that we're using them in our 00:00:51.600 --> 00:01:00.960 24 SSD server with that massive raid array so click right here to learn 00:00:58.600 --> 00:01:04.359 more hey he there we 00:01:04.560 --> 00:01:10.400 go all right we're back in business 00:01:08.600 --> 00:01:16.159 business of breakage it's really great that Intel 00:01:13.080 --> 00:01:19.520 Provisions uh you know these emergency 00:01:16.159 --> 00:01:22.600 mounting mechanisms into their socket 00:01:19.520 --> 00:01:23.520 designs they think of everything I think 00:01:22.600 --> 00:01:29.240 we're on look at 00:01:25.840 --> 00:01:31.280 that hey hey there you go she's posting 00:01:29.240 --> 00:01:35.799 with two gpus installed let's get that other cooler on okay so we're booted 00:01:33.799 --> 00:01:41.479 into Windows it looks like all the hardware is working oh we haven't put in 00:01:38.720 --> 00:01:46.320 the second Titan x yet but there's time there's time for that I think we have to 00:01:44.159 --> 00:01:50.840 close out this video though so we'll finish up with just a validation that 00:01:48.439 --> 00:01:56.520 everything's in here so we can see the maximum speed of our CPUs how many 00:01:52.880 --> 00:01:58.479 sockets how many cores and threads we 00:01:56.520 --> 00:02:02.600 have stay tuned guys we're going to Benchmark this thing I want to check out 00:02:00.360 --> 00:02:08.360 power consumption want to see if we can Crush some leaderboards um so stay tuned 00:02:05.439 --> 00:02:13.200 for that in the meantime like this video now for you guys it won't really 00:02:10.759 --> 00:02:18.519 seem like we've made a ton of progress since last week it has been a full week 00:02:16.400 --> 00:02:24.480 since I've even been able to touch this but actually I've aside from cleaning up 00:02:21.239 --> 00:02:26.120 the desk area here I have been hard at 00:02:24.480 --> 00:02:32.519 work on trying to get this thing working now you can see it's working now but the 00:02:29.879 --> 00:02:37.920 issue is that this motherboard is really designed for Server use not workstation 00:02:35.640 --> 00:02:42.480 use and in spite of mine and super micro's best efforts to dink around with 00:02:40.599 --> 00:02:47.760 a bazillion different bio settings and all of that stuff we got one card going 00:02:45.280 --> 00:02:52.920 but we couldn't get two and I really wanted two Titan x's in here not for SLI 00:02:50.599 --> 00:03:00.239 or gaming or anything but for more compute performance more of dat Cuda 00:02:57.360 --> 00:03:07.519 so I have been waiting for two things to arrive number one is ASUS's whatever 00:03:03.680 --> 00:03:11.239 this thing is Z10 pe- D16 this is an 00:03:07.519 --> 00:03:14.040 ASUS dual socket board as well as the 00:03:11.239 --> 00:03:20.080 dual 10 gbit Nick that I'm going to need since that board doesn't have two 10 00:03:16.959 --> 00:03:22.640 gbit land ports on board the other thing 00:03:20.080 --> 00:03:27.440 I thought I needed is these Noctua narrow mounting brackets 00:03:25.239 --> 00:03:31.239 but uh I don't think that board actually uses the narrow ilm so I may not 00:03:29.400 --> 00:03:35.080 actually really need these anymore my zip ties were a great 00:03:33.319 --> 00:03:41.360 solution anyway I am so excited actually super 00:03:38.120 --> 00:03:42.840 micro has sent an additional board as 00:03:41.360 --> 00:03:47.239 well they sent one of their workstation ones so we're still not locked into 00:03:45.920 --> 00:03:51.360 using this one especially because their workstation one does have the land ports 00:03:49.400 --> 00:03:58.319 we need which means I can reuse that card somewhere else but you know JJ was 00:03:56.159 --> 00:04:04.439 all up in my business on Twitter being like yo lonus you should really be using 00:04:00.439 --> 00:04:05.599 Aus for everything so I uh I figured I 00:04:04.439 --> 00:04:11.640 might as well at least give them a chance so here it is my friends the 00:04:08.560 --> 00:04:14.480 unboxing experience so many 00:04:11.640 --> 00:04:19.680 CDs and that my friends is the board itself so as I suspected it does not use 00:04:17.359 --> 00:04:22.680 the narrow ilm so that was all for nothing 00:04:23.120 --> 00:04:29.120 potentially and there we go still got 16 00:04:26.120 --> 00:04:32.800 memory slots still got two LGA 2011 3 00:04:29.120 --> 00:04:34.800 sockets it still uses 24 pin 8 Pin 8 Pin 00:04:32.800 --> 00:04:40.400 and waa what's that we've got an additional four pin power down here so 00:04:37.440 --> 00:04:45.080 that is three CPU power connectors pretty fantastic we've got six SATA 00:04:42.720 --> 00:04:50.280 ports another four down here we've got whatever the devil all this stuff is USB 00:04:47.320 --> 00:04:55.759 3 on a front panel header' got an m.2 socket which is pretty interesting 00:04:53.960 --> 00:04:59.919 so let's go ahead and get this baby uh get this baby rigged up maybe with 00:04:57.440 --> 00:05:02.680 proper mounting hardware this time yeah I know right well people keep 00:05:01.400 --> 00:05:05.520 complaining that I'm not doing it properly so this time I'm going to do it 00:05:04.479 --> 00:05:10.800 properly they're going to end up with a boring video then no one's going to be 00:05:08.320 --> 00:05:14.039 happy except maybe a Seuss to not see their Hardware being 00:05:12.320 --> 00:05:19.120 mistreated okay now here's something you know many 00:05:16.840 --> 00:05:24.440 of you haters probably aren't noticing but go back and look for it me grounding 00:05:21.960 --> 00:05:32.680 myself out while I'm working I actually do do it I kill surprisingly Little 00:05:28.479 --> 00:05:32.680 Hardware almost kill a lot of 00:05:36.039 --> 00:05:44.680 Hardware eight okay it just counts down 00:05:40.919 --> 00:05:46.520 it it here it's here it just counts down 00:05:44.680 --> 00:05:55.280 the entire range of post codes that it can display this is not fair like 00:05:52.280 --> 00:05:55.280 why 00:05:55.600 --> 00:06:05.680 okay hey 00:06:01.000 --> 00:06:07.800 um well gee man I have had I have had 00:06:05.680 --> 00:06:12.800 better I went through hell with that super micro board and I was just hoping 00:06:10.800 --> 00:06:17.919 a s quality man I'm going to plug everything in and it's going to be like 00:06:14.840 --> 00:06:19.960 rocking out and I am I'm in a super sad 00:06:17.919 --> 00:06:24.000 state right now do you need sort of the full 00:06:21.000 --> 00:06:25.319 update uh yeah I I'm not aware of any of 00:06:24.000 --> 00:06:29.199 this I mean I guess it's something you were working on with with Roger yeah if 00:06:27.319 --> 00:06:32.680 you can at least let let me know what what Bo you have I can see what Insight 00:06:30.759 --> 00:06:36.400 I can give you and then hopefully we can help help get things moving forward okay 00:06:34.919 --> 00:06:41.960 uh in consumer based boards because there's a much higher likelihood that consumers are utilizing higher-end cards 00:06:39.280 --> 00:06:45.840 and newer cards that have uh GOP and nalization policy support uh we have an 00:06:44.319 --> 00:06:51.400 auto routine built in that should have neiz that detect it allow it to become 00:06:47.720 --> 00:06:53.599 in play but okay so we actually got it 00:06:51.400 --> 00:06:58.280 to post and we didn't get that error with the network card in the Bottom PC 00:06:55.960 --> 00:07:02.479 Express 16x slot but we ran into a new thing where we couldn't see any of our 00:06:59.400 --> 00:07:03.919 our boot devices so we pulled that out 00:07:02.479 --> 00:07:08.680 and we're trying again now so one way or another I'm not 00:07:06.080 --> 00:07:14.080 getting this video out on Sunday am I uh uh it's it still might be a 00:07:12.319 --> 00:07:18.400 possibility might be a possibility depends I I I might be able to actually 00:07:16.160 --> 00:07:23.080 get a hold of them today it just depends on if I can get a hold of our PM team to 00:07:20.520 --> 00:07:29.599 to get them to get me request that so unfortunately ASUS's BIOS team was not 00:07:26.440 --> 00:07:32.120 available to work on a custom BIOS for 00:07:29.599 --> 00:07:36.080 me on the weekend so we're going to have to settle for One Titan X but I don't 00:07:34.759 --> 00:07:41.879 want to leave you guys hanging any longer so we are going to run some 00:07:38.240 --> 00:07:46.080 rudimentary benchmarks with our two 2699 00:07:41.879 --> 00:07:48.919 v3s so our 36 cores our 128 gigs of RAM 00:07:46.080 --> 00:07:52.440 and a single titanx graphics card so we're going to kick things off and one 00:07:50.759 --> 00:07:58.960 of the things that I want to look at well a number of things I want to look at is power consumption temps now that 00:07:56.840 --> 00:08:02.680 we have proper coolers on them I want to see what what kind of turboing we get 00:08:00.960 --> 00:08:08.960 out of a something like a gaming workload and of course I want to see 00:08:05.280 --> 00:08:11.800 that cinebench number check this out 00:08:08.960 --> 00:08:17.400 idle power consumption is under 100 Watts from the wall closer to 90 Watts 00:08:15.520 --> 00:08:22.360 this is with an 80 plus Platinum efficiency power supply but still that 00:08:20.560 --> 00:08:26.960 means it's actually only consuming somewhere in the neighborhood of 85 00:08:24.199 --> 00:08:30.840 Watts at idle of course the story is going to change somewhat underload so 00:08:28.840 --> 00:08:36.519 let's go ahead and see how much we can actually draw here so at idle the CPU 00:08:33.560 --> 00:08:41.800 was sitting at about 1.2 GHz now it's turboing up to 2.6 when we're hitting it 00:08:39.519 --> 00:08:46.320 with a full load so you can see we've started a stability test here in Ida 64 00:08:44.680 --> 00:08:52.000 and our CP usage is sitting in the neighborhood of 98 to probably 100 by 00:08:49.760 --> 00:08:58.079 the time it refreshes again percent and check that out that is with just the 00:08:55.839 --> 00:09:01.839 CPUs working that's the kind of power consumption we'd expect to see see from 00:08:59.519 --> 00:09:08.760 a gaming rig including graphics cards but these are not CPUs for the faint of 00:09:05.000 --> 00:09:11.560 heart I think I saw that touch 500 watts 00:09:08.760 --> 00:09:15.800 just hitting the CPUs so let's go ahead and let's add system memory does it let 00:09:14.120 --> 00:09:21.360 me change the stress test mid-flight it really doesn't like 00:09:19.560 --> 00:09:27.040 that let's see okay so memory usage is closing in 00:09:24.000 --> 00:09:29.720 at 100% now and you can see that thanks 00:09:27.040 --> 00:09:34.480 to the efficiency of the ddr4 modules from Kingston that we're using we're 00:09:31.839 --> 00:09:39.839 still hovering around that 500 watt Mark but now we're consistently or much more 00:09:36.720 --> 00:09:42.480 frequently around that 500 watt Mark now 00:09:39.839 --> 00:09:48.760 we're going to throw GPU into the mix and see what happens so now with the GPU 00:09:45.880 --> 00:09:54.040 running we're actually seeing sustained loads in the high 600s and I've even 00:09:50.640 --> 00:09:55.800 seen Peaks at around 700 Watts but 00:09:54.040 --> 00:10:01.040 what's cool is we're still running at our max turbo frequency uh CPU temps are 00:09:58.800 --> 00:10:06.880 still very much under control in the low 60s to high 50s range in spite of the 00:10:04.079 --> 00:10:12.519 fact that the air is noticeably warmer in a sphere around this open test bench 00:10:10.640 --> 00:10:17.160 computer so this is good news it means everything's stable and we can proceed 00:10:14.600 --> 00:10:21.519 with the rest of our benchmarks next up is everyone's favorite multicore CPU 00:10:19.920 --> 00:10:28.079 benchmarks c a bench R15 let's go ahead and run that bad boy 00:10:25.000 --> 00:10:31.200 so that is what it looks like to see 72 00:10:28.079 --> 00:10:35.320 threads ripped through cine bench I have 00:10:31.200 --> 00:10:39.720 never seen anything quite like it 00:10:35.320 --> 00:10:44.600 wow so that's a score of 00:10:39.720 --> 00:10:48.560 3981 in cinebench R15 so for perspective 00:10:44.600 --> 00:10:52.720 that's what a 12 core xon at 2.66 GHz is 00:10:48.560 --> 00:10:55.839 capable of and uh we completely left 00:10:52.720 --> 00:11:00.120 that in the Dust by more than 00:10:55.839 --> 00:11:01.959 3x 3D Mark I wasn't expecting in to get 00:11:00.120 --> 00:11:05.560 like Powerhouse amazing results thanks to the low clock speed of the CPU and 00:11:03.720 --> 00:11:09.680 the fact that we're only running one GPU so it's not exactly optimized for it but 00:11:07.720 --> 00:11:13.360 I was expecting a little bit better on the physics score that's actually 00:11:11.320 --> 00:11:19.639 significantly lower than you can do on a 4770k showing that while it is a 00:11:16.079 --> 00:11:23.160 multi-threaded test it can't handle 72 00:11:19.639 --> 00:11:25.160 threads not so much so for our last 00:11:23.160 --> 00:11:30.760 trick we're going to try and top the real bench so that's ASUS's Rog 00:11:27.440 --> 00:11:32.079 Benchmark score board without an Rog 00:11:30.760 --> 00:11:38.560 motherboard I mean it's still an isus motherboard I'm sure they won't be too upset about it but oh I want to be able 00:11:36.160 --> 00:11:43.839 to have a look at how our multi-threaded CPU is helping us during this Benchmark 00:11:41.639 --> 00:11:49.440 so let's get that baby open it looks like we're using like one 00:11:47.040 --> 00:11:53.399 of our threads maybe two two maybe two threads I have no idea if that image 00:11:51.600 --> 00:11:57.800 editing score is any good but the encoding Benchmark is running and we're 00:11:55.079 --> 00:12:03.639 finally getting some CPU utilization only 50% Max so far oh oh oh here we go 00:12:01.160 --> 00:12:08.800 here we go okay so our final test is heavy multitasking and once again I am 00:12:06.600 --> 00:12:15.160 not getting necessarily the results I was hoping for we have not yet we have 00:12:12.440 --> 00:12:23.000 not yet broken our second SE oh yeah there it is yes so our score was not 00:12:19.600 --> 00:12:26.160 that great system score 00:12:23.000 --> 00:12:29.199 91,000 is which puts us 00:12:26.160 --> 00:12:32.800 actually pretty far down the leaderboard 00:12:29.199 --> 00:12:35.079 something about the Dual socket is not 00:12:32.800 --> 00:12:39.560 appreciated by a lot of the benchmarks that we've been playing around with here 00:12:36.920 --> 00:12:42.519 but this is something that we kind of expected and I think ties pretty well 00:12:41.079 --> 00:12:49.839 into the conclusion for this video so I'm actually going to go I'm going to stand next to it here this kind of a 00:12:46.720 --> 00:12:52.240 system is not for desktop use we know 00:12:49.839 --> 00:12:56.480 this and it's I had a lot of people criticizing me on social media about the 00:12:54.760 --> 00:13:00.800 fact that we're even running Windows on it because this is the kind of thing 00:12:58.639 --> 00:13:04.440 that if you're doing some kind of serious number crunching that for 00:13:02.639 --> 00:13:07.839 whatever reason doesn't benefit from GPU you really need CPU for it for some 00:13:06.120 --> 00:13:11.360 reason that's what this is for and it's becoming more and more of a n case 00:13:09.519 --> 00:13:15.240 scenario in a lot of cases something like Linux might be better for those 00:13:13.680 --> 00:13:19.839 particular workloads but what people don't know is what we're actually doing 00:13:17.519 --> 00:13:23.880 with this system and what we'll be doing with it is not going to be General usage 00:13:22.440 --> 00:13:28.279 where we've demonstrated that you probably shouldn't have 36 cores and 72 00:13:26.120 --> 00:13:31.800 threads what we'll be doing with it is we'll be running a specialized piece of 00:13:29.880 --> 00:13:38.639 software right now the front runner is sorin and squeeze server um to 00:13:35.600 --> 00:13:40.839 significantly reduce the output times of 00:13:38.639 --> 00:13:47.399 our videos so that we can turn them around much more quickly as well as 00:13:44.360 --> 00:13:49.680 actually transcode footage upon 00:13:47.399 --> 00:13:53.720 ingesting off of our cameras so that it's easier for our PCS to work with 00:13:52.120 --> 00:13:58.519 while we're editing the videos creating something called a proxy so that is what 00:13:56.720 --> 00:14:02.040 this system is for and for that it will be excellent so you guys are going to 00:13:59.759 --> 00:14:05.440 want to stay tuned where we'll show well it hooked up to the 10 gbit Network 00:14:04.000 --> 00:14:08.639 we're going to show its performance rendering videos over the network once 00:14:07.440 --> 00:14:13.240 we've actually got the software we're using finalized and that is going to be 00:14:11.000 --> 00:14:18.639 a sight to behold even if running desktop grade benchmarks with CPUs that 00:14:15.720 --> 00:14:22.160 are running at well not that high clock speeds wasn't that impressive today so 00:14:20.880 --> 00:14:26.639 thanks for watching guys like the video if you liked it dislike it if you thought it sucked leave a comment 00:14:24.480 --> 00:14:29.560 preferably at the link to our Forum in the video description if you want to 00:14:27.920 --> 00:14:32.680 discuss it also linked in the video description you can buy a cool t-shirt 00:14:30.920 --> 00:14:37.399 like this one although this particular one is over on Teespring so you're going 00:14:35.720 --> 00:14:42.399 to want to uh go ahead and check out the special link in order to get one of our 00:14:39.279 --> 00:14:43.680 first campaign lonus Tech tip shirts 00:14:42.399 --> 00:14:47.519 also linked in the video description you can change your Amazon bookmark one with our affiliate code and I think that 00:14:45.959 --> 00:14:50.759 pretty much wraps it up thanks again for watching and as always don't forget to 00:14:49.199 --> 00:14:54.279 subscribe wait that's a like I don't know what I'm doing anymore it's 00:14:52.240 --> 00:14:59.160 Saturday shouldn't even be working I'm not even supposed to be at work 00:14:56.759 --> 00:15:04.320 today three internet points if you know the reference or I'm not even supposed 00:15:00.680 --> 00:15:04.320 to be here I didn't even get it right 00:15:12.680 --> 00:15:15.680 whatever