Prime95 Not using 100%

[Prime95]

Originally Posted by kladner

I think I am not fully understanding your part about 'extra translation step'.

Prime95 no longer cares about Windows or Linux or Intel or AMD logical core numbering schemes.

Prime95 now uses the hwloc library to enumerate logical cores. To see hwloc's hardware analysis, do an options/benchmark, pick any old FFT size. In results.txt will be hwloc's topology analysis.

For example, my 4 core, 8 threads Mac:

 Machine#0 (total=16777216KB, CPUModel="Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz", Backend=Darwin, OSName=Darwin, OSRelease=13.4.0, OSVersion="Darwin Kernel Version 13.4.0: Mon Jan 11 18:17:34 PST 2016; root:xnu-2422.115.15~1/RELEASE_X86_64", HostName=george-woltmans-macbook-pro-2.local, Architecture=x86_64, Backend=x86, hwlocVersion=1.11.4, ProcessName=Prime95)
  NUMANode#0 (local=16777216KB, total=16777216KB)
    L3#0 (size=6144KB, linesize=64)
      L2#0 (size=256KB, linesize=64, ways=8)
        L1d#0 (size=32KB, linesize=64)
          Core#0 (cpuset: 0x00000003)
            PU#0 (cpuset: 0x00000001)
            PU#1 (cpuset: 0x00000002)
      L2#1 (size=256KB, linesize=64, ways=8)
        L1d#1 (size=32KB, linesize=64)
          Core#1 (cpuset: 0x0000000c)
            PU#2 (cpuset: 0x00000004)
            PU#3 (cpuset: 0x00000008)
      L2#2 (size=256KB, linesize=64, ways=8)
        L1d#2 (size=32KB, linesize=64)
          Core#2 (cpuset: 0x00000030)
            PU#4 (cpuset: 0x00000010)
            PU#5 (cpuset: 0x00000020)
      L2#3 (size=256KB, linesize=64, ways=8)
        L1d#3 (size=32KB, linesize=64)
          Core#3 (cpuset: 0x000000c0)
            PU#6 (cpuset: 0x00000040)
            PU#7 (cpuset: 0x00000080)

The "PU#" (I don't know what PU is an abbreviation for) is the logical core number.

[GP2]

Originally Posted by Prime95

The "PU#" (I don't know what PU is an abbreviation for) is the logical core number.

Maybe the same "PU" as in "CPU".

[Dubslow]

Originally Posted by GP2

Maybe the same "PU" as in "CPU".

Speaking seriously: there's a good chance it's not the same, since it's not really a processing unit -- more of a fancy piece of management silicon.

Speaking somewhat less seriously: perhaps it stands for "Pipeline Umpire"

[Mark Rose]

Originally Posted by GP2

Maybe the same "PU" as in "CPU".

Indeed.

https://www.open-mpi.org/projects/hw...66bfb175a8dc55