MAXCPUS - mt86.cfg

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • yoobongc
    Junior Member
    • Oct 2024
    • 7

    #1

    MAXCPUS - mt86.cfg

    1. running configuration : Intel GNR-AP CRB (dual CPUs - each CPU has 144 physical cores) + 24 DIMMs (12 DIMMs per each CPU)

    2. configured mt86.cfg
    - TSTLIST=6
    - CPUSEL=PARALLEL
    - MAXCPUS=512

    3. Problem statement:
    When running MemTest86, I thought all 288 cores would run simultaneously,
    but in reality, they seem to be split into groups of 144 cores taking turns running... Is this normal?
    How can I make all 288 cores run MemTest simultaneously?
  • yoobongc
    Junior Member
    • Oct 2024
    • 7

    #2
    In addition, I am using MemTest86 11.7 Pro version now.

    Comment

    • Simon (PassMark)
      Administrator
      • Apr 2021
      • 336

      #3
      By default MemTest86 only runs on physical cores, which is why it shows 144 active.

      To use all 288, you can either:

      Go to Config → CPU Selection in MemTest86 and enable Hyperthreading, or
      Remove hash in front the 'ENABLEHT=1' line to the mt86.cfg file in the \EFI\BOOT\ folder of the USB drive.

      Running on the extra logical cores usually doesn't add much to memory testing

      Comment

      • yoobongc
        Junior Member
        • Oct 2024
        • 7

        #4
        I have tried both case which are ENABLEHT=0 and ENABLEHT=1, results are not changed.
        Our server is DUAL Physical CPU which a CPU has 144 cores.
        I would like to run TWO CPUs are running simulaneoursly.
        But it loos like a CPU is running and another CPU is running righr after a CPU task is ended.

        Comment

        • yoobongc
          Junior Member
          • Oct 2024
          • 7

          #5
          for your better understanding...Click image for larger version

Name:	image.png
Views:	12
Size:	1.78 MB
ID:	60873

          Comment

          • David (PassMark)
            Administrator
            • Jan 2003
            • 11126

            #6
            Running on this many cores is a waste of time from the point of view of testing the memory. Once the memory bandwidth is saturated (which probably happens with around 40 cores in this case, given the number of memory channels) add more is a waste of time and will likely give negative performance. (i.e. get slower due to cache evictions and thrashing).

            But if you would like to send us a debug log we can take a look at it.

            Also for the upcoming V12 release we will both provide better support for Intel GNR and selecting active CPU cores.

            Comment

            Working...