this post was submitted on 26 Dec 2024
33 points (97.1% liked)
Hardware
895 readers
533 users here now
All things related to technology hardware, with a focus on computing hardware.
Rules (Click to Expand):
-
Follow the Lemmy.world Rules - https://mastodon.world/about
-
Be kind. No bullying, harassment, racism, sexism etc. against other users.
-
No Spam, illegal content, or NSFW content.
-
Please stay on topic, adjacent topics (e.g. software) are fine if they are strongly relevant to technology hardware. Another example would be business news for hardware-focused companies.
-
Please try and post original sources when possible (as opposed to summaries).
-
If posting an archived version of the article, please include a URL link to the original article in the body of the post.
Some other hardware communities across Lemmy:
- Augmented Reality - [email protected]
- Gaming Laptops - [email protected]
- Laptops - [email protected]
- Linux Hardware - [email protected]
- Mechanical Keyboards - [email protected]
- Microcontrollers - [email protected]
- Monitors - [email protected]
- Raspberry Pi - [email protected]
- Retro Computing - [email protected]
- Single Board Computers - [email protected]
- Virtual Reality - [email protected]
Icon by "icon lauk" under CC BY 3.0
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
[lack of] Diminishing performance returns isn't the reason I was excited about the idea though :( I just don't want to worry running something on the "wrong" CCD.
If you had to keep it cool by clocking so low that a normal 16 core outperforms it, it doesn't make sense.
Or maybe I'm completely wrong, and they'll release a dual 3d cache cpu a couple months after they start selling the 9950x3d to maximize profit
The cache location being flipped mitigates some of the clock speed gap (and I personally don't like how inefficient recent-gen CPUs are in lightly threaded workloads, so skimming 5% off the 1T clockspeed without affecting the nT clockspeed isn't much of a con for me personally). I don't mind being virtually-imperceptibly (<5%) slower in workloads that are not sensitive to cache if the tradeoff is having the workloads that are sensitive to cache always, without fail gaining that respective benefit.
Haha, I think they would have both a branding problem for the SKU (what do they call it?), and significant backlash from both press and the public if they did that, but it's not unheard of for a hardware manufacturer to trip over themselves doing something like that :P