Thursday, December 26
Daily News Stuff 26 December 2019
Taking Time Out To Digest Edition
Taking Time Out To Digest Edition
Tech News
- 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
Disclaimer: Pop a Poppler in your mouth,
When you come to Fishy Joe's,
What they're made of is a mystery,
Where they come from, no one knows.
You can pick 'em, you can lick 'em,
You can chew 'em, you can stick 'em,
If you promise not to sue us,
You can shove one up your nose.
Posted by: Pixy Misa at
10:40 PM
| Comments (4)
| Add Comment
| Trackbacks (Suck)
Post contains 374 words, total size 3 kb.
1
That TokuDB kind of gives you an appreciation for the compatibility-with-broken-products stuff Microsoft does, as seen in Raymond Chen's blog, like the video card that, when queried for capabilities, said "yeah, I do that", no matter what you asked it, even if you asked it for something undefined.
Posted by: Rick C at Friday, December 27 2019 12:40 AM (Iwkd4)
2
Yes. It should at least give a warning if you define foreign key constraints, but nope, they just silently disappear.
Posted by: Pixy Misa at Friday, December 27 2019 12:59 AM (PiXy!)
3
Early in the life of my current employer, Production converted everything to MySQL Cluster without either testing in a pre-release environment or discussing it with development. It had no foreign key support, and just silently dropped them out of the schemas. It was also incredibly fragile and buggy, and when we finally convinced them that it corrupted data under load, they insisted that they couldn't re-enable foreign keys without weeks of testing in QA.
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.
-j
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.
-j
Posted by: J Greely at Saturday, December 28 2019 08:20 AM (ZlYZd)
4
Ouch. I test my hobby projects better than that.
Posted by: Pixy Misa at Sunday, December 29 2019 01:27 AM (PiXy!)
52kb generated in CPU 0.0214, elapsed 0.1663 seconds.
58 queries taking 0.1512 seconds, 349 records returned.
Powered by Minx 1.1.6c-pink.
58 queries taking 0.1512 seconds, 349 records returned.
Powered by Minx 1.1.6c-pink.