• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

FRONTPAGE UL Benchmark Launches CPU Profile Benchmarking Software

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
Ok, I've done some more testing, and am again reminded how much of a pain power limited running is as clocks are all over the place, making it harder to see patterns. As such I can't go into as much detail as I hope with current data.

For single thread, there may be a weak relationship with CPU clock after all. We're looking at perhaps 2% delta off ideal scaling for a 2x difference in clock change. This disappears when you run more than 1 thread.

Rocket Lake score/core/clock is about 20% higher than Comet Lake when both run at typical clocks. Before anyone says score/core/clock shouldn't matter as we normalised for clock, look at the line above. I could probably improve the peak score/core/clock some more by running lower clock, but don't intend to do that.

There is some non-ideal scaling as the thread count increases. As such, ignore previous statements about gains from HT/SMT, as it will be under-represented due to the thread scaling. I'll have to retest with disabled cores to get a better picture on this. This is in part based on my 12 core Skylake-X results, and I also used Johan45's 5950X post earlier as an additional data point, although I'm less confident in that as I have to estimate running clocks from the screenshot.

Edit: just did a run on 7920X limited to 4 cores. The effective HT scaling is ~17% which compares max & 8 thread scores relative to 1, 2 thread scores, normalised for clock/cores. I didn't use 4 cores as there was a drop in performance there. 24 thread vs 1-2 thread only implied 4% scaling. Looking at the other data, there is a noticeable drop in score when threads = cores. Similarly looking at the 5950X results, with some rough clock normalisation the 8 thread result is equivalent to about 7 cores, and the 16 thread result is about 12 cores worth. We do have the real cores in that situation so we can't say that loss is due to SMT, unless Windows scheduler is keeping it on one CCX or something like that.

Given all the above, the core/thread scaling is not as good as I thought it was initially. Cinebench still scales better across more cores/threads. Here we do have a mild diminishing return effect as thread counts increase. For modern games I think the 8 to 18 thread results are probably most interesting.
 
Would not a good example would have been running the i9-7920x @ 4c/8t and then 8c/8t? Not sure as I still have not got to play. The memory is also and nice look as there is not improvement. Does this mean the program stays in the CPU L1/L2/L3(??) and never makes it to system memory?? Will you be able to see improve from go from the i7-26xx/37xx/47xx (4c/8t) CPUÂ’s over Intels release?? This is also = AMDÂ’s CPUÂ’s..
 
Would not a good example would have been running the i9-7920x @ 4c/8t and then 8c/8t? Not sure as I still have not got to play. The memory is also and nice look as there is not improvement. Does this mean the program stays in the CPU L1/L2/L3(??) and never makes it to system memory?? Will you be able to see improve from go from the i7-26xx/37xx/47xx (4c/8t) CPUÂ’s over Intels release?? This is also = AMDÂ’s CPUÂ’s..

I did 4c8t and the 8c8t is implicitly covered when it was in normal 12c24t state.

Not seeing ran scaling doesn't mean it doesn't use ram, it must do at some point. Just, the amount it does use it is low enough not to be a significant factor.

I'm pretty much tested out now. I'm not motivated to add older CPUs to it. Maybe I'd add Broadwell next time I have the system out, but wont go out of my way to do it.
 
I saw that this is now a Beta test at hwbot.org. Single core and all core scores are counted. I see the single bench becoming like superpi - limit cpu to 1-2 cores for max speed..
 
Back