Thunder 57
Diamond Member
- Aug 19, 2007
- 3,747
- 6,334
- 136
Compared to the 12-core X3D?
Yes. It will depend on models and price though.
Compared to the 12-core X3D?
There's certainly no way to avoid a price increase I acceptYes. It will depend on models and price though.
Same for AMD then, since they'll also have a 48T CPU on 2 channel memory in 2026/7.I just can't imagine anyone but the cinebench graphers buying a 48 core CPU on 2 channel memory in 2026/7.
It says that the MT performance will be better given a certain power consumption restriction. And I'm talking about the range of ~150W TDP which is expected for NVL-S.That says nothing about Novalake being better than Zen 6.
Because you could have a 50W 16+32 chip just by clocking it low enough. But your performance will suck.
But that s exactly perf/watt, they encode a file using Handbrake, there s nothing that is pushed here, the 285K consume 35% more, 222W vs 159W for the first pass that is lightly threaded and 263W vs 196W for the second pass that is heavily mutlithreaded,We’re talking about different things.
I was talking about perf/watt when not pushing the cores to max perf (or max TDP).
That's part of the explanation, but not all of it. It's about the efficiency of the cores too.This has little to do with cores lol and everything to do with AMD paying a constant 20-25W penalty due to an antiquated IOD (which they will no longer be paying with Zen 6: looking at you, Strix Halo).
I was talking about perf/watt when you limit the power consumption, so it does not run at stock TDP.But that s exactly perf/watt, they encode a file using Handbrake, there s nothing that is pushed here, the 285K consume 35% more, 222W vs 159W for the first pass that is lightly threaded and 263W vs 196W for the second pass that is heavily mutlithreaded,
The 9950X has 42% better perf/watt since it s actually 2% faster in this task, the review i linked used an older Handbrake version where it s 5-6% slower but it has been updated by Computerbase in their recent CPU round up.
Yes. It will depend on models and price though.
Certainly, there was a lot of power consumption at idle, right?That's part of the explanation, but not all of it. It's about the efficiency of the cores too.
Also, Zen5 IOD does not consume 20-25W more than corresponding dies for Intel. It's not like the ones Intel uses do not consume any power at all.
The problem with that graph is that it's total system power consumption at idle, so it's hard to know what parts of the system consume what part of the power. GPU, IOD, memory, SSD, CPU cores, mother board, etc. So you cannot tell how much the IOD consumes based on that graph.Certainly, there was a lot of power consumption at idle, right?
I know thatThe problem with that graph is that it's total system power consumption at idle, so it's hard to know what parts of the system consume what part of the power. GPU, IOD, memory, SSD, CPU cores, mother board, etc.
Ummm...do greater number of threads not exist? More cores to handle OS/background threads means less time wasted in context switching. Overall system responsiveness is improved. More cores may not scale all that well but they are not going to be completely useless. One thing that is not measured/benchmarked very well is real user workloads where they may have multiple applications open at the same time and switching between them frequently. Not all threads are I/O bound so the membw may not be an issue in the majority of the cases. I don't see why increasing cores should be considered a problem. If you build them, use cases will follow soon enough.day 9592 of anandtech posters pretending there's a mythical workload that scales infinitely with cores, while not giving a crap about membw AND not needing to be correct (aka requiring ECC from workstation/HEDT boards).
I want a multi-way SMT...Ummm...do greater number of threads not exist? More cores to handle OS/background threads means less time wasted in context switching. Overall system responsiveness is improved. More cores may not scale all that well but they are not going to be completely useless. One thing that is not measured/benchmarked very well is real user workloads where they may have multiple applications open at the same time and switching between them frequently. Not all threads are I/O bound so the membw may not be an issue in the majority of the cases. I don't see why increasing cores should be considered a problem. If you build them, use cases will follow soon enough.
If the decoder gets split again in a future µArch that doesn't seem like such a stretch.I want a multi-way SMT...
I want a multi-way SMT...
@Cheesecake16I want a multi-way SMT...
Given *mont loses efficiency to *cove cores it seems like perf/area optimisation is their main target, so better to just try and make the cores smaller and have moar going by the core spam strategy Nova Lake is rumored to employ.@Cheesecake16
Tricky question (seems to me): Does SMT4 and SMT8 benefit CPUs with more pipeline stages and higher speeds? Is SMT missing in "-mont architecture" CPUs because they are low clocked so SMT throughput wouldn't be high enough to warrant wasting transistors on it?
Yeah but doesn't it make you wonder? If only 5% more transistor cost could double the resource utilization of the mont cores, why not do that???Given *mont loses efficiency to *cove cores it seems like perf/area optimisation is their main target, so better to just try and make the cores smaller and have moar going by the core cpam Nova Lake is rumored to have.
It's an irrrelevant market. Very few people want/need more cores or threads. Intel wouldn't be forced to drop 265KF to $230 to sell a meaningful number of them, whereas AMD is laughing all the way to the bank selling an 8-core chip for $470, despite the 265KF being a better choice in literally every single way except that one use case the majority of users care about.Ummm...do greater number of threads not exist? More cores to handle OS/background threads means less time wasted in context switching. Overall system responsiveness is improved. More cores may not scale all that well but they are not going to be completely useless. One thing that is not measured/benchmarked very well is real user workloads where they may have multiple applications open at the same time and switching between them frequently. Not all threads are I/O bound so the membw may not be an issue in the majority of the cases. I don't see why increasing cores should be considered a problem. If you build them, use cases will follow soon enough.
I don't think the mont architecture is inefficient…Given *mont loses efficiency to *cove cores it seems like perf/area optimisation is their main target, so better to just try and make the cores smaller and have moar going by the core spam strategy Nova Lake is rumored to employ.
Sure, many users don't need a lot of cores.It's an irrrelevant market. Very few people want/need more cores or threads. Intel wouldn't be forced to drop 265KF to $230 to sell a meaningful number of them, whereas AMD is laughing all the way to the bank selling an 8-core chip for $470, despite the 265KF being a better choice in literally every single way except that one use case the majority of users care about.
And adding more cores to your core interconnect, be it ring or something else, isn't free.
I didn't say inefficient, I said less efficient than *cove cores of the same generation for IPC.I don't think the mont architecture is inefficient…