HWiNFO v7.32 released

Martin

HWiNFO Author
Staff member
HWiNFO v7.32 available.

Changes:
  • Added reporting of Core Performance Order and PBO Scalar for AMD Raphael.
  • Added monitoring of Energy Performance Preference for later AMD APUs.
  • Fixed reporting of CPPC order on systems with gaps in APIC IDs.
  • Enhanced sensor monitoring on ASUS X670 series.
  • Fixed a possible hang during USB enumeration when Xbox 360 is connected.
  • Enhanced sensor monitoring on EVGA Z790 series.
  • Fixed a rare case when Nuvoton NCT6799 sensor might not be found.
  • Added early support of some AMD Zen5 families.
  • Enhanced support of Intel Meteor Lake and Granite Rapids.
  • Enhanced sensor monitoring on ASRock X670E series.
  • Enabled VRM monitoring on some ASRock mainboards.
  • Enhanced sensor monitoring on ASUS B650 and Z790 series.
  • Added hovering delay for sensor tooltips.
  • Enhanced sensor monitoring on Intel 13th Gen NUC series.
  • Added monitoring of GPU Thermal Limit for NVIDIA GPUs.
  • Added monitoring of GIGABYTE AORUS P1200W PSU.
  • Updated translations for several languages.
 
HWiNFO v7.32 Beta available.

Changes:
  • Added reporting of Core Performance Order and PBO Scalar for AMD Raphael.
  • Added monitoring of Energy Performance Preference for later AMD APUs.
  • Fixed reporting of CPPC order on systems with gaps in APIC IDs.
  • Enhanced sensor monitoring on ASUS X670 series.
  • Fixed a possible hang during USB enumeration when Xbox 360 is connected.
  • Enhanced sensor monitoring on EVGA Z790 series.
  • Fixed a rare case when Nuvoton NCT6799 sensor might not be found.
  • Added early support of some AMD Zen5 families.
  • Enhanced support of Intel Meteor Lake and Granite Rapids.
  • Enhanced sensor monitoring on ASRock X670E series.
  • Enabled VRM monitoring on some ASRock mainboards.
  • Enhanced sensor monitoring on ASUS B650 and Z790 series.
  • Added hovering delay for sensor tooltips.
  • Enhanced sensor monitoring on Intel 13th Gen NUC series.
  • Added monitoring of GPU Thermal Limit for NVIDIA GPUs.
  • Added monitoring of GIGABYTE AORUS P1200W PSU.
  • Updated translations for several languages.
hi! what does Core Performance Order mean ? I have next result: 4, 2, 6, 1, 3, 5, 7, 8, 10, 12, 16, 14, 9, 13, 11, 15 but don`t know how it help me :)
 
hi! what does Core Performance Order mean ? I have next result: 4, 2, 6, 1, 3, 5, 7, 8, 10, 12, 16, 14, 9, 13, 11, 15 but don`t know how it help me :)

Read second part (perf #n/n)

Untitled_88.png

In the simplest words the first number is the the order that windows scheduler will/should load the cores depending on the amount of the workload and the second is the evaluation of AMD on the cores based mostly on the highest clock ability and other characteristics as required operating voltage for a specific frequency, current... and such.

When a CPU has 2 chiplets (12 and 16 core CPUs) one of them is higher binned than the other, as better/faster.
I have a 12 core CPU with 2 chiplets (6 cores per chiplet) and as you can see the cores are evaluated slightly differently than your 16 core (2x8core)
I have an order of 1,2,3,4,5 and 8 on the first (lets say primary) chiplet and 6,7,9,10,11,12 on the second.
Windows in this case as we can see on the first perf# number will load first the 1,2 (that why those 2 have the highest max and avg clock frequency) and then if workload (and threads) keep increasing it will load sequentially 3,4,5 and 8. It will not load 6,7 before 8 because those 2 cores are on the second-ary chiplet. And when threads of the same process are placed on different chiplets then you have the biggest latency penalty form core cross talk on different chiplets. This chiplet cross talk is decreasing performance by a small or large amount depending on the application, game and type of workload in general.
 
Back
Top