-
Notifications
You must be signed in to change notification settings - Fork 78
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
a108283
commit 6174c35
Showing
5 changed files
with
661 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
6174c35
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As for the HFI warning... it seems neither
taskset
norcgroups
are sufficient to pin tasks to the E cores. At least my tries were to no avail: this is an i9-12900T in extensive mode: http://ix.io/4doc7-zip MIPS when pinned to
cpu0
is 6356 while pinned tocpu16
(supposedly an E core) is 4401 which is simply impossible with an E core. Different cpufreq policies do apply (cpu0
= 4900 MHz,cpu16
= 3600 MHz) and most probably this makes the difference while also the benchmark run pinned to an E core has been executed on a P core in reality with reduced clockspeed.Same with multi-threaded numbers: CPUs 0-15 score 35600 7-zip MIPS (P cores with SMT enabled) while when pinned to CPUs 16-23 the score is 31800 which is impossible with E cores and again hints at the benchmark in reality running on the P cores.
The only somewhat useful
sbc-bench
mode with these hybrid Intel thingies isMODE=extensive sbc-bench -G
to generate Geekbench scores and compare there 'all cores' vs. 'only P cores' to get an idea about the impact the (missing) E cores have: http://ix.io/4do3 or to be more precise: https://browser.geekbench.com/v5/cpu/compare/18004391?baseline=18004480This works for the sole reason
sbc-bench
sending CPUs 16-23 offline prior to calling Geekbench. The other variant to only test on E cores doesn't work sincecpu0
can't be sent offline.Further reading: https://www.agner.org/forum/viewtopic.php?f=1&t=79