Thursday, December 26
Taking Time Out To Digest Edition
- The Threadripper 3970X is a 32 core 280W monster. But how does it perform if you dial the power back a little? (WCCFTech)
Thirdripper has configurable TDP, the same as Ryzen 3000. So this doesn't even require manual undervolting; just fire up Ryzen Master and pick your TDP target.
At 180W it still delivers 90% of full multi-core performance, and at 140W it manages 82%. That gives us a good idea of the performance of the upcoming 3990X - double the cores, double the power budget back up to 280W, and it will be 64% faster than the 3970X. Of course, it's not as simple as that, because memory bandwidth won't double, but memory bus power consumption won't double either, and cache will double...
Cut to 95W the 3970X is clearly struggling and achieves only 48% of its full potential. At that point it is actually slower than the Intel 10980XE.
- Samsung is investing $116 billion into its chip manufacturing division. (The Verge)
That's quite a lot. TSMC's ascendence has effectively been bankrolled by Apple, and Samsung are their only real competition at this point.
- Cloudflare has taken on the role of supporting CDNJS. (Cloudflare)
While Cloudflare were providing the CDN for CDNJS, the project was run until now entirely by volunteers. When some automated scripts broke last month and the volunteers didn't have the resources to fix it right away, the future of CDNJS seemed in doubt.
So this is, on the whole, a good thing.
- TokuDB doesn't support foreign key constraints. Doesn't even save your definitions, it just drops them straight onto the floor. That's not a critical issue here because I control the application code as well as the database definitions, but it's a bit limiting.
- YouTube's latest target is cat videos. I'm not even kidding.
Movie of the Day
Posted by: Rick C at Friday, December 27 2019 12:40 AM (Iwkd4)
Posted by: Pixy Misa at Friday, December 27 2019 12:59 AM (PiXy!)
To which we pointed out that QA had always been testing with foreign keys enabled, because none of their environments ever got Cluster-fucked. The problem wasn't testing whether they worked, it was rebuilding the integrity of the Production DB so they could.
Posted by: J Greely at Saturday, December 28 2019 08:20 AM (ZlYZd)
Posted by: Pixy Misa at Sunday, December 29 2019 01:27 AM (PiXy!)
58 queries taking 0.1459 seconds, 339 records returned.
Powered by Minx 1.1.6c-pink.