1 00:00:00,080 --> 00:00:06,640 In the 2 years since AMD last launched a 2 00:00:03,439 --> 00:00:08,800 Threadripper CPU, I got braces. I got a 3 00:00:06,640 --> 00:00:17,119 firet truck. I cooled a bunch of stuff. And I prepared for this day, this day of 4 00:00:13,519 --> 00:00:19,760 today's when I will unbox, install, and 5 00:00:17,119 --> 00:00:24,080 find out how many points AMD's king of the Thread Rippers, the Ryzen 9980X, can 6 00:00:22,560 --> 00:00:32,160 get us in Cinebench and various other points measuring softwares. can 64 Zen 5 7 00:00:28,560 --> 00:00:34,960 cores and over 300 million bytes of 8 00:00:32,160 --> 00:00:39,440 cache ascend us to dizzying heights the likes of which high-end desktops have 9 00:00:36,880 --> 00:00:45,120 never seen before or is this going to be a classic modern Yeah. Yeah, I guess the 10 00:00:42,000 --> 00:00:50,120 new one's faster. To find out, I'm going 11 00:00:45,120 --> 00:00:50,120 to have to brave Shamada Peak. 12 00:00:55,440 --> 00:01:02,960 After I brave today's segue to our sponsor, Threat Locker. Everywhere you 13 00:01:01,199 --> 00:01:07,439 store data can be susceptible to cyber attacks, and that even includes plugged 14 00:01:04,720 --> 00:01:11,200 in USB drives. Learn how Threat Locker's storage control can prevent unwanted 15 00:01:09,600 --> 00:01:15,600 users from accessing your company secrets by using our link in the video 16 00:01:13,840 --> 00:01:21,439 description. When it comes to the numbers on the spec sheet, AMD's new 17 00:01:17,920 --> 00:01:23,680 Threadripper 9980X has more in common 18 00:01:21,439 --> 00:01:28,640 with the last gen than it seems to have different. It's got the same number of 19 00:01:25,840 --> 00:01:33,759 processing cores, 64 cores and 128 threads with the same admittedly massive 20 00:01:31,200 --> 00:01:40,159 L2 and L3 caches operating at the same base clock frequency of 3.2 2 GHz in the 21 00:01:37,040 --> 00:01:44,320 same STR5 socket at the same 350 watt 22 00:01:40,159 --> 00:01:47,840 TDP. So, AMD, what took 2 years? I don't 23 00:01:44,320 --> 00:01:51,520 know. How about 80 freaking lanes of 24 00:01:47,840 --> 00:01:54,560 PCIe Gen 5? That's almost double the 25 00:01:51,520 --> 00:01:57,759 Piddley 48 lanes of yestery year 7980X. 26 00:01:54,560 --> 00:02:01,200 And okay, yes, Intel Xeon W3500 series 27 00:01:57,759 --> 00:02:02,960 can do up to 112 lanes of PCIe Gen 5. 28 00:02:01,200 --> 00:02:06,640 But I think the folks who care about that are probably more likely to be 29 00:02:04,960 --> 00:02:11,360 interested in AMD's new Threadripper Pro chips that launched literally the 30 00:02:09,360 --> 00:02:15,840 day that we were reviewing this script. But then AMD didn't send those over for 31 00:02:13,280 --> 00:02:19,840 comparison. So I guess if I want transparency in my CPU launches, I'll 32 00:02:18,000 --> 00:02:23,440 have to do it myself with this transparent screwdriver available now at 33 00:02:21,920 --> 00:02:27,760 ltstore.com. Anywh who, there's more to love about 34 00:02:25,520 --> 00:02:31,599 the chips that we do have here today, so let's focus on these. AMD was already 35 00:02:30,239 --> 00:02:36,480 ahead of their competition in performance, and the best got even 36 00:02:34,319 --> 00:02:41,680 better today. The move from AMD's older Zen 4 architecture to Zen 5 netted them 37 00:02:39,440 --> 00:02:46,400 a pretty juicy double-digit performance increase, even at the exact same clock 38 00:02:43,760 --> 00:02:50,400 speed. And adding a bit of extra spice, is the fact that the higher core count 39 00:02:48,160 --> 00:02:55,519 chips this generation should be able to boost even higher, as high as 5.4 GHz in 40 00:02:53,680 --> 00:02:59,920 lightly threaded loads. And that's out of the box. As is tradition, AMD's 41 00:02:58,080 --> 00:03:03,599 latest Threadripper chips are factory unlocked for overclocking. But before we 42 00:03:02,080 --> 00:03:08,000 get to that, I want to talk about another outofthe-box improvement, and 43 00:03:05,680 --> 00:03:12,720 that's memory. Threadripper's quad channel memory controller is going from 44 00:03:10,480 --> 00:03:18,959 it's going from being rated for a pitily 5200 megat transfers per second to a 45 00:03:15,280 --> 00:03:23,280 juicy 6400 megat transfers per second. 46 00:03:18,959 --> 00:03:26,000 Now, we've got only 128 gigs of this 47 00:03:23,280 --> 00:03:29,519 overclockable ECC register and RDM memory to play with today, courtesy of 48 00:03:27,920 --> 00:03:37,840 AMD, who provided this hardware for testing. But the 9980X supports up to 1 49 00:03:33,280 --> 00:03:41,519 terabte of memory. That's up to four 256 50 00:03:37,840 --> 00:03:44,000 gig modules. What a time to be alive. 51 00:03:41,519 --> 00:03:47,440 Pies. Now, the motherboard isn't the main focus for today, but I do want to 52 00:03:46,000 --> 00:03:50,720 throw some storage in it, and I can use this as an opportunity to highlight the 53 00:03:49,200 --> 00:03:55,840 kinds of configurations that are possible thanks to all the PCIe lanes on 54 00:03:53,360 --> 00:04:02,080 this new CPU. Down here, we've got five PCIe x6 slots. Now, they're all not 55 00:03:58,480 --> 00:04:04,799 running at 16 Gen 5, but these two are. 56 00:04:02,080 --> 00:04:11,920 This is Gen 5 by 8, and these two are gen 4x4 and gen 4x6. We've then still 57 00:04:08,239 --> 00:04:15,599 got PCIe lanes for dual Gen 5 slots. 58 00:04:11,920 --> 00:04:17,680 another Gen 4 slot and plenty of PCIe 59 00:04:15,599 --> 00:04:23,040 left for unbelievable onboard connectivity. I'm talking Wi-Fi 7, super 60 00:04:19,919 --> 00:04:25,280 fast USB, and both 2 and a half gig and 61 00:04:23,040 --> 00:04:30,400 10 gig networking. And because there's so much PCIe on the CPU, those are all 62 00:04:28,000 --> 00:04:32,880 running without any kind of switching. So, you're not going to have to worry 63 00:04:31,440 --> 00:04:36,960 about bottlenecks if you're hitting your, you know, AI accelerator super 64 00:04:35,199 --> 00:04:41,440 hard here and your high-speed storage array and your high-speed networking all 65 00:04:39,199 --> 00:04:46,400 at the same time. Of course, it won't do any of that without a power supply. 66 00:04:44,560 --> 00:04:53,199 Now, the keenite among you might have noticed that this is a 1600 W power 67 00:04:50,639 --> 00:04:57,680 supply. But Lionus, you might ask, you mentioned a 350 W TDP earlier. What's 68 00:04:56,320 --> 00:05:03,120 the point of this kind of ludicrous overkill? Well, that's a great question. 69 00:05:00,320 --> 00:05:07,600 As it turns out, AMD not only allows overclocking, they even provided some 70 00:05:05,360 --> 00:05:11,840 guidelines for what you might need. And um 71 00:05:09,600 --> 00:05:18,440 is this right? They recommend a 1,500 watt power 72 00:05:15,440 --> 00:05:18,440 supply. 73 00:05:20,720 --> 00:05:25,680 I'm going to need a minute to process this, which is probably fine cuz it's 74 00:05:24,080 --> 00:05:30,720 going to take me a solid 15 minutes to wire this thing up. On top of the usual 75 00:05:28,479 --> 00:05:36,000 dual 8pin CPU power connectors that you would find on a high-end platform like 76 00:05:32,320 --> 00:05:40,240 this, for the CPU alone, there are two 77 00:05:36,000 --> 00:05:42,240 more 12vt PCIe 8pin connectors. And then 78 00:05:40,240 --> 00:05:48,800 to help with auxiliary power for the PCIe slots, there's a six pin and an 8 79 00:05:44,960 --> 00:05:53,039 pin PCIe. And that ignores what about 80 00:05:48,800 --> 00:05:54,880 second 24 pin. Although this one is less 81 00:05:53,039 --> 00:05:59,520 about providing more power and more about allowing you to run dual power 82 00:05:57,039 --> 00:06:05,360 supplies that will both turn on at the same time when you turn on the system. 83 00:06:02,560 --> 00:06:10,000 That is flipping hilarious. I haven't plugged in anything but the motherboard 84 00:06:07,120 --> 00:06:14,160 yet. And uh we're going to need some pretty 85 00:06:12,479 --> 00:06:20,240 special cooling for this as well. Red ripper specific AIO uses a triple 120 mm 86 00:06:17,360 --> 00:06:24,080 radiator. And you notice the uh pump block unit is pretty low profile. That's 87 00:06:22,319 --> 00:06:28,199 cuz the pump is actually here embedded in the radiator. Cool beans. 88 00:06:30,479 --> 00:06:39,400 I hate myself for saying this, but wow, this is a pretty reasonable size for a 89 00:06:34,560 --> 00:06:39,400 5090. All right, big moment. 90 00:06:40,880 --> 00:06:47,520 Oh, wow. That was quick. I was actually expecting it to take a 91 00:06:44,960 --> 00:06:50,880 very, very, very, very long time to boot. Apparently, the first time we 92 00:06:49,280 --> 00:06:55,360 tried to fire this up, it took about 5 minutes for memory training, which I 93 00:06:53,680 --> 00:07:01,759 mean, compared to epic, not even that bad. Hey, there we go. 128 gigs. Went 94 00:06:58,960 --> 00:07:06,080 right to DDR56400 because that's not an expo profile. That's just the speed this 95 00:07:04,000 --> 00:07:10,080 flipping stuff runs at. Man, that's really surprising for our high-end 96 00:07:07,599 --> 00:07:15,319 desktop almost workstation platform. Our SSD is picked up. All we got to do is 97 00:07:17,120 --> 00:07:23,440 Okay, we've seen this before, but we've never seen this with well, okay, we've 98 00:07:21,919 --> 00:07:28,960 probably seen this with Zen 5, cores, but not Threadripper ones that run this 99 00:07:25,840 --> 00:07:30,880 fast. Now, obviously, we know that a 100 00:07:28,960 --> 00:07:34,639 system like this is not meant for gaming, but I mean, come on. You got 64 101 00:07:34,080 --> 00:07:40,880 cores >> running at like 5.4 4 GHz >> up two. I should have 102 00:07:38,720 --> 00:07:44,560 >> up two. That's basically a gaming CPU right there. >> Let's play some cyber punk. Did we talk 103 00:07:43,440 --> 00:07:48,720 about pricing yet? >> It's >> Oh, I wasn't going to tell them yet. 104 00:07:47,199 --> 00:07:54,319 >> And this is where they all tune out. >> Yeah. I mean, we're still getting like 105 00:07:50,880 --> 00:07:55,360 1% of like 8090 in the elevator. 106 00:07:54,319 --> 00:08:00,560 >> I don't want to include this. >> But it's 95% usage on the GPU. 107 00:07:59,039 --> 00:08:06,560 >> I mean, oh, you're not wrong. >> 13%. >> What the hell? What is our CPU at 97°? 108 00:08:06,000 --> 00:08:11,039 Fair enough. >> Uh do do you smell it though? >> Hold on. Hold on. Let me just 109 00:08:10,400 --> 00:08:15,599 >> Okay. >> Yeah. >> I think frame view just is not 110 00:08:14,160 --> 00:08:19,120 >> there's too many threads. It's confusing >> configured for this. Yes. 111 00:08:18,240 --> 00:08:24,720 >> 128 threads. >> Yeah. We're only drawing up 100 watts 112 00:08:21,520 --> 00:08:26,160 and we're doing like 48°. So now you 113 00:08:24,720 --> 00:08:29,919 might think, hey, if it does it so effortlessly, it must be the fastest 114 00:08:27,759 --> 00:08:34,399 gaming CPU. But that's not really the case. We benchmarked this puppy against 115 00:08:32,159 --> 00:08:42,719 the top of the line of AMD's regular consumer desktop chips, the 9950 X3D, 116 00:08:37,919 --> 00:08:45,600 and it mostly keeps up mostly thanks to 117 00:08:42,719 --> 00:08:49,839 its high clock speeds. But in Cyberpunk, it exhibited some anomalous performance 118 00:08:47,360 --> 00:08:57,680 that AMD was able to replicate on their side. So neat, I guess. Good gaming 119 00:08:53,680 --> 00:08:59,120 performance for a lot more money. Um, 120 00:08:57,680 --> 00:09:04,399 like a lot more. We got the price this morning, right? Yeah, it's uh it's 121 00:09:02,080 --> 00:09:12,720 $5,000. It's the same as the last thread. It didn't go up. Hey, hey, let's 122 00:09:08,880 --> 00:09:14,720 go. To be clear, like the screwdriver, 123 00:09:12,720 --> 00:09:18,880 as excited as we are about something not going up in price, buying into a 124 00:09:16,480 --> 00:09:23,600 platform like this at any price is pretty dumb. Even if it's just for 125 00:09:20,640 --> 00:09:26,880 bragging rights, that's still dumb. But it doesn't mean this is a dumb product. 126 00:09:25,120 --> 00:09:30,959 To be clear, he forgot to change the setting off from 10 minutes to just like 127 00:09:28,640 --> 00:09:33,680 render once. Uh, but it's done. It already restarted. That was under a 128 00:09:32,240 --> 00:09:37,920 minute. We're at 909. >> 6870 129 00:09:35,680 --> 00:09:43,120 points. >> That's a lot for 24. 130 00:09:40,880 --> 00:09:46,800 >> What did our 16 core Ryzen get? >> 24 27. 131 00:09:45,440 --> 00:09:49,200 >> Okay, that is a lot. >> Five. >> This is just a lot. 132 00:09:48,560 --> 00:09:54,000 >> Yeah. >> Okay, hold on a second. I'm running the stress test version, which actually is 133 00:09:52,720 --> 00:10:02,480 >> Oh, yeah. We should look at our wattage. Pretty good opportunity here. >> Yo, 65° that's totally fine. And 350 W 134 00:10:00,720 --> 00:10:07,279 exactly what we'd expect based on the TDP of this chip. But what's interesting 135 00:10:04,560 --> 00:10:10,560 is we haven't enabled PBO yet. And right now it's only running at dude average 136 00:10:09,120 --> 00:10:17,200 effective clock 4.3. >> Pretty good on across across 64 cores. 137 00:10:14,640 --> 00:10:22,160 >> That's pretty wild, >> dude. This thing rips. So gaming pretty 138 00:10:20,079 --> 00:10:25,440 dumb. But if you're at work stuck on a consumer platform or an older 139 00:10:24,079 --> 00:10:30,640 workstation that's holding back your productivity, by all means pick up a 140 00:10:28,399 --> 00:10:35,519 scribe driver and write a polite memo to procurement to ask for one of these 141 00:10:32,560 --> 00:10:40,000 babies. But with that said, if you're already on last gen Threadripper, even 142 00:10:37,920 --> 00:10:44,720 though this chip is just a drop-in replacement, unless you need the extra 143 00:10:42,240 --> 00:10:50,000 PCIe lanes or specifically more memory bandwidth, it might not be worth the 144 00:10:47,200 --> 00:10:53,839 expense. or is it an example where you might really benefit from a Thread 145 00:10:51,760 --> 00:10:59,200 Ripper 9000 would be AI and machine learning. While there is no NPU or 146 00:10:56,640 --> 00:11:03,360 neural processor on this thing or even an integrated GPU at all, let's be real. 147 00:11:01,920 --> 00:11:08,640 If you're spending this kind of money on a workstation, it's not to run AI on 148 00:11:05,839 --> 00:11:14,480 your stupid CPU. is to take advantage of all those PCIe lanes to run as many GPUs 149 00:11:12,240 --> 00:11:20,000 as possible to form a little local supercluster and then let those chew up 150 00:11:16,959 --> 00:11:22,240 your inference models. For funsies, we 151 00:11:20,000 --> 00:11:29,040 did run some quick procon AI computer vision tests on the CPU and as expected, 152 00:11:25,920 --> 00:11:31,519 it's not for that. It actually even lost 153 00:11:29,040 --> 00:11:35,040 to our 9950X3D, probably because of higher latency 154 00:11:32,959 --> 00:11:42,079 between the CPU memory modules and also the lower boost frequency. It actually 155 00:11:37,200 --> 00:11:43,680 even lost to a GTX 1060, a $300 GPU from 156 00:11:42,079 --> 00:11:49,519 2016. But when you've got 80 PCIe Gen 5 lanes, 157 00:11:47,120 --> 00:11:53,200 you're going to be hooking up quad 5090s or even workstation grade cards, which 158 00:11:51,519 --> 00:11:58,079 is going to make our 1060 look like a bad joke. So, we agree with AMD's 159 00:11:56,079 --> 00:11:59,600 assessment that Threadripper 9000 is good for AI. 160 00:11:59,200 --> 00:12:06,560 >> Yes, >> it's just more as a supporting cast member. >> Yeah, like me. 161 00:12:03,760 --> 00:12:10,240 >> Rather than an AI compute star, >> not like you. 162 00:12:09,279 --> 00:12:16,240 >> Not an AI comput star. >> What does this even mean? >> I don't know. >> Let's see how fast it runs some stuff 163 00:12:13,440 --> 00:12:21,519 it's actually intended for, like spec workstations. While AMD focused on Intel 164 00:12:19,519 --> 00:12:26,880 comparisons in their reviewers guide, we recognized that nobody cares about what 165 00:12:24,000 --> 00:12:32,800 Intel's doing in Workstation right now. So instead, we put it up against AMD's 166 00:12:29,279 --> 00:12:35,680 top consumer chip, the Ryzen 9 9950X3D 167 00:12:32,800 --> 00:12:43,360 to see what the justification is for spending 10x, almost 8x on your CPU. 168 00:12:40,959 --> 00:12:47,120 >> 7zip pretty compelling. We're looking at 169 00:12:45,120 --> 00:12:51,360 nearly double the performance in both compression and decompression. 170 00:12:49,519 --> 00:12:55,440 >> Yeah, it costs more than five times as much money. But this is what winning 171 00:12:53,200 --> 00:13:00,880 looks like. Let's go. I don't care if we barely win. 172 00:12:58,480 --> 00:13:06,639 We've won. Actually, no. We won by a lot. Y Cruncher sub 8 seconds. 173 00:13:04,160 --> 00:13:11,680 >> M delicious moon pies. >> Moon pies. What a time to be alive. 174 00:13:09,040 --> 00:13:19,440 >> And how about Spec Workstation? Here we go from a 2.12 CPU score on our 9950 X3D 175 00:13:15,680 --> 00:13:22,000 to 4.16 on our latest Threadripper. We 176 00:13:19,440 --> 00:13:26,399 see some obliteration in the actual performance across a range 177 00:13:24,720 --> 00:13:31,600 of CPU oriented professional applications. What a monster. 178 00:13:29,360 --> 00:13:36,560 >> Speaking of, it was three times faster in Blender, rendering our monster 179 00:13:33,040 --> 00:13:39,200 benchmark scene in just one minute. Man, 180 00:13:36,560 --> 00:13:42,880 I remember when like finishing BMW in a minute was impressive. 181 00:13:40,480 --> 00:13:46,079 >> Probably does in like 10 seconds now. >> It probably spends more time spooling up 182 00:13:44,480 --> 00:13:49,839 the job than actually doing it. What about GDAU compile though? I mean, after 183 00:13:48,000 --> 00:13:54,000 all, that might be something you'd care about if you're buying a processor like 184 00:13:51,360 --> 00:14:03,680 this. And uh wow, that poor poor 9950X 3D. Next up is 185 00:13:59,040 --> 00:14:06,320 Handbreak. And uh h it's better, but not 186 00:14:03,680 --> 00:14:10,560 that much better. At least not for AV1. Maybe X264. 187 00:14:08,000 --> 00:14:14,800 >> No, it's about the same uplift there as well. So, you know, there's uplift, 188 00:14:13,120 --> 00:14:18,000 >> but not as much as I'd like for the price. >> Not two or three times as fast like 189 00:14:16,880 --> 00:14:22,720 we're seeing some of these other. >> But hear me out. >> Sure. >> All of this is while we're encumbered by 190 00:14:20,720 --> 00:14:25,680 a measly 350 W power limit. >> That's very true. >> What if we just turn up the turbulent 191 00:14:25,199 --> 00:14:29,360 juice? >> PBO. >> Let's go. 192 00:14:28,320 --> 00:14:33,519 >> Next thing we're going to do is we're going into precision boost overdrive 193 00:14:31,360 --> 00:14:38,560 advanced. We're going to set our PPT limit to, I don't know, John said 194 00:14:36,079 --> 00:14:41,040 something astronomical. So, I'm going to put 1 billion. 195 00:14:40,639 --> 00:14:47,360 >> That's good. >> We're also going to turn up our maximum CPU boost clock override to 200. So, 196 00:14:46,000 --> 00:14:53,199 that's across all cores. >> Let's go. >> And then for our curve optimizer, we're 197 00:14:49,600 --> 00:14:55,120 going to set all cores to five. 198 00:14:53,199 --> 00:15:00,399 >> Good luck, everybody. >> Let's see if this little AIO can handle 199 00:14:57,040 --> 00:15:03,519 it. It's a 360 mil rad, which is great. 200 00:15:00,399 --> 00:15:05,680 >> It's great. Good job, Silver Stone. 201 00:15:03,519 --> 00:15:07,760 >> It honestly it handled 350 watts pretty well. Let's be real here. 202 00:15:07,120 --> 00:15:12,279 >> Easy money. >> Yeah. >> And it warms my arm 203 00:15:12,399 --> 00:15:23,920 >> and my heart. Cinebench multicore. Here we go. 41C 48 C 48 C 52 C. 204 00:15:22,000 --> 00:15:29,360 >> It's only 39. Okay, now it's pulling it. 400 watts. 390 205 00:15:25,360 --> 00:15:31,760 >> 390 watts. out. Honestly, 206 00:15:29,360 --> 00:15:36,000 not as much as I expected. In fairness, these are kind of the AMD recommended 207 00:15:34,320 --> 00:15:41,760 settings and it's clocking higher. 208 00:15:38,240 --> 00:15:44,320 >> Dude, we're hitting 4.5 GHz on 64 cores 209 00:15:41,760 --> 00:15:48,399 and at only 390 W. >> Like, I mean that. I mean that. That's 210 00:15:47,199 --> 00:15:55,040 kind of incredible. >> I think we can do more though. >> You think so? >> I think we can do more. We've set our 211 00:15:51,920 --> 00:15:56,959 peak current limits to uh 212 00:15:55,040 --> 00:16:00,560 1 million milliamps. 213 00:15:59,199 --> 00:16:06,000 We increased our precision boost overdrive scaler to 3x. We set the 214 00:16:03,120 --> 00:16:09,519 platform thermal throttle limit to 100°. >> Hell yeah. 215 00:16:06,720 --> 00:16:13,759 >> Hell yeah. And then the one other thing that I was looking at in here is maybe 216 00:16:11,680 --> 00:16:16,720 we should disable this >> throttling. >> Yeah, just let her rip. 217 00:16:15,839 --> 00:16:22,079 >> Yeah, they're good. >> Let her rip. And then peak current 218 00:16:19,360 --> 00:16:25,519 control. Who needs that? Not me. >> Oh, buddy. 219 00:16:23,920 --> 00:16:30,720 >> 72° 550 watts. 78°. 220 00:16:29,680 --> 00:16:36,560 Yes. >> I I think it's going down. >> I hear the fans going. 221 00:16:34,399 --> 00:16:41,600 >> Oh, yeah. >> Oh, buddy. >> 78 533. 222 00:16:40,079 --> 00:16:46,560 >> Look at this frequency. >> 85. 223 00:16:43,839 --> 00:16:51,680 You think we can hit 5 GHz all core if we get a bigger cooler on it? 224 00:16:50,079 --> 00:16:55,360 >> I mean, ADC, >> anything's possible. I feel like it's 225 00:16:53,759 --> 00:16:58,880 got more to give, but we're thermally limited. If only there was some way to 226 00:16:57,120 --> 00:17:04,959 get it colder. Our chiller's broken right now. I just don't really have any 227 00:17:01,120 --> 00:17:07,919 ideas for uh 228 00:17:04,959 --> 00:17:12,559 We got a lot of ice. Seriously, we're going ice bucket. We're doing the ice 229 00:17:09,919 --> 00:17:15,760 bucket challenge like it's 2018. When was ice bucket challenge? 230 00:17:14,160 --> 00:17:21,679 >> 2016, actually. No, it's probably earlier than that. Oh god, I'm so old. 231 00:17:18,000 --> 00:17:24,799 Here we go. Oh god, 232 00:17:21,679 --> 00:17:26,720 what's happening? Why are we doing this? 233 00:17:24,799 --> 00:17:31,440 That's horrible. Why would you tell me to do that? 234 00:17:29,840 --> 00:17:34,640 Under normal circumstances, we would do a bunch of insulation on the motherboard 235 00:17:32,960 --> 00:17:37,760 to ensure that condensation doesn't damage it. But we're going to be running 236 00:17:36,160 --> 00:17:41,039 this for such a short period of time. So, as long as we keep an eye on the 237 00:17:39,200 --> 00:17:45,280 outside of the block, I'm not actually worried about it being a problem. Um, 238 00:17:43,200 --> 00:17:48,280 here, this is coming really soon, ltstore.com.a, 239 00:17:49,280 --> 00:17:56,000 and compatible with our little uh key holder, power bar holders, so you can 240 00:17:54,640 --> 00:17:59,200 stick your bits wherever they need to go. Uh, I think it's this one. And now, 241 00:17:57,919 --> 00:18:03,720 I'm going to do a good job of testing this pump bet. 242 00:18:03,840 --> 00:18:09,280 Where's our block? Oh, that would have been terrible. What? 243 00:18:07,600 --> 00:18:13,360 >> I just had this running down to the floor, blah blah, etc. EK, they've gone 244 00:18:12,640 --> 00:18:17,200 through some >> We've had it for a long time, but you know, these are all forward and 245 00:18:15,679 --> 00:18:21,600 backwards compatible with Threadripper. >> Oh, cool. >> At least on this socket. Yeah. 246 00:18:19,440 --> 00:18:24,320 >> So, uh, even though it's an older block, >> it'll work on the new STR5. 247 00:18:23,679 --> 00:18:28,000 >> Oh, shoot. >> Yeah, there's a little bit of gunk in there. >> Oh, balls. 248 00:18:26,880 --> 00:18:31,280 >> Is it too much? >> Yeah. Yeah. >> I mean, we only got to run it for like 249 00:18:30,000 --> 00:18:38,080 10 minutes. >> Okay, there we go. And yikes. 250 00:18:35,360 --> 00:18:41,919 What the heck kind of water did we put in here? That's the problem is any junk 251 00:18:40,240 --> 00:18:45,440 that does grow in a loop or anything that does contaminate it usually ends up 252 00:18:43,919 --> 00:18:49,039 in the CPU block because that's where all these tight little fins are. You know, 253 00:18:47,280 --> 00:18:52,559 >> obviously this kind of setup wouldn't work for a long-term deployment. But 254 00:18:51,280 --> 00:18:58,559 >> we're just going to see if we can push this thing a little further. You want 5 GHz? 255 00:18:54,960 --> 00:19:01,039 >> Yeah, we we saw 4.8 4.85. 256 00:18:58,559 --> 00:19:03,679 >> I know, but it's on 64 cores. >> Yeah, but now we've got a bucket of ice. 257 00:19:02,720 --> 00:19:10,000 >> That's true. >> Do it. All right. How's our temps? 258 00:19:06,400 --> 00:19:11,679 Casual 13°. Let's go, boys. 259 00:19:10,000 --> 00:19:16,480 >> Yes. >> What? What? It's getting cold. 260 00:19:14,640 --> 00:19:20,480 >> This is amazing. >> We've done >> I had no idea what you guys were doing 261 00:19:18,720 --> 00:19:24,640 when you said bucket. >> It's cooling solutions for cool kids. 262 00:19:22,799 --> 00:19:27,039 >> Yeah, we've done this multiple times. >> Yeah. >> Well, what do you think? How hot do you 263 00:19:26,480 --> 00:19:32,000 think it's ice? >> My CPU is at like 8C. Like, this works. 264 00:19:30,400 --> 00:19:35,919 This is not a stupid thing to do. >> Yeah. Well, >> well, okay. Okay. Longterm maybe, but 265 00:19:34,799 --> 00:19:38,799 temporary it's great. >> Yeah. >> 365 a lot. 266 00:19:38,080 --> 00:19:42,960 >> Wait, what? >> 8 485. No, it's still going. Just let it go. >> Okay, she's going. She's cooking. 267 00:19:41,919 --> 00:19:49,840 >> I don't know if it'll go past 500 though. 490. >> Same. 268 00:19:46,080 --> 00:19:52,160 >> Yeah, we're stuck at 4.85. 269 00:19:52,160 --> 00:19:57,490 >> We weren't thermally limited. >> No, I'm partic I'm, you know, I'm 270 00:19:55,919 --> 00:19:59,760 wellelmed. 271 00:19:59,760 --> 00:20:10,400 Appropriately wellelmed. Not over or under, just appropriately wellelmed. 272 00:20:06,720 --> 00:20:12,400 >> Good chip and shockingly not that hard 273 00:20:10,400 --> 00:20:18,080 to cool. So if you were to build a workstation around this thing, I mean, 274 00:20:15,120 --> 00:20:21,280 >> 360 mil AIO is honestly way good enough. >> And you can chuck it right in the 275 00:20:19,840 --> 00:20:29,200 existing machine you had that was already handling a Threadripper cuz it's running at exactly the same TDP. I 276 00:20:24,880 --> 00:20:33,440 set the multiplier to 50. Um, PBO let me 277 00:20:29,200 --> 00:20:36,240 down. And we're at 630 W now. So my 278 00:20:33,440 --> 00:20:38,720 scale here is not sufficient anymore. No, we didn't cut the screen count. Oh, 279 00:20:37,679 --> 00:20:43,200 she's going, boys. >> Oh my god. What'd you change? >> We're over 5 GHz. 280 00:20:41,039 --> 00:20:48,080 >> No. 640 watts. What do you change? What did you change? >> I just turned the multiplier up. With 281 00:20:45,840 --> 00:20:52,880 that said, I don't necessarily know it's worth upgrading from a 7950X, but I 282 00:20:51,360 --> 00:20:56,400 never say no to more performance at the same wattage and core count. And if you 283 00:20:55,039 --> 00:20:59,520 do want to pick up anything we showed today, hey, I never say no to you 284 00:20:58,159 --> 00:21:05,280 clicking the affiliate link in the video description below. As for everyone else 285 00:21:03,760 --> 00:21:08,559 who doesn't need one of these, maybe we'll link some sensible chips for 286 00:21:06,799 --> 00:21:12,080 gamers down there. And make sure you're subscribed for our upcoming look at 287 00:21:09,919 --> 00:21:19,919 Threadripper Pro, which is coming to the WRX90 chipset with support for up to 288 00:21:15,760 --> 00:21:23,039 128 PCIe Gen 5 lanes, up to 96 cores, 289 00:21:19,919 --> 00:21:26,159 and up to eight channels of DDR5 Ardoms 290 00:21:23,039 --> 00:21:27,840 supporting up to 2 terab of RAM. My 291 00:21:26,159 --> 00:21:33,440 goodness, getting all hot and bothered. Time to 292 00:21:30,320 --> 00:21:36,000 cool off with this refreshing ice bucket 293 00:21:33,440 --> 00:21:39,600 to our sponsor, Threat Locker. Imagine if someone could unlock the door to your 294 00:21:37,760 --> 00:21:43,440 home and steal all your stuff just by giving it a few knocks. Well, Threat 295 00:21:41,200 --> 00:21:48,080 Locker Storage Control lets your IT team provide application level access to 296 00:21:45,360 --> 00:21:52,240 storage locations while blocking all other users and programs from accessing 297 00:21:49,840 --> 00:21:56,240 it. Basically, the idea is your door can only open if you're around to let 298 00:21:54,159 --> 00:22:00,640 someone in. If a storage device is blocked, then the non-approved users 299 00:21:58,320 --> 00:22:04,799 will be given a prompt to request access that only administrators can approve. 300 00:22:02,960 --> 00:22:08,799 that doesn't just include local folders or networks, but can even include 301 00:22:06,480 --> 00:22:13,360 plugged in USB drives. It can even block cookie access for specific browsers. And 302 00:22:11,679 --> 00:22:17,440 you can get a highle view of every single instance of storage access with a 303 00:22:15,440 --> 00:22:21,200 central log that shows exact files that were copied and the devices serial 304 00:22:19,440 --> 00:22:24,720 number, whether it's on the network or remote. So, don't wait. Take the 305 00:22:23,120 --> 00:22:28,960 necessary steps to keep your company's data safe by checking out Threat Locker 306 00:22:26,960 --> 00:22:33,039 Storage Control using our link in the video description. If you guys enjoyed 307 00:22:31,280 --> 00:22:39,280 this video, make sure to check out the time we ran Crisis entirely on a CPU, 308 00:22:36,400 --> 00:22:44,559 like a a many core CPU like this one with no GPU. It was cray cray. Editor's 309 00:22:42,240 --> 00:22:49,760 note. This is like in case we can get more. 310 00:22:47,280 --> 00:22:55,440 Oh god, it can do even more. >> All crashed. No, it can't. 311 00:22:51,520 --> 00:22:56,720 >> We were at 770 watts. 5.3 GHz. 312 00:22:55,440 --> 00:23:02,159 >> Yes. Maybe >> five plus GHz. It's really >> That's a lot on 64 cores. Yeah.