Announcement

Collapse
No announcement yet.

Linux Performance Test in Ubuntu 20.04 Running Under Windows Subsystem for Linux 2

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux Performance Test in Ubuntu 20.04 Running Under Windows Subsystem for Linux 2

    I'm trying the run the Linux version of Performance Test in Ubunto 20.04 installed under WSL2 in Windows 10 x64. It launches, but doesn't generates results, with zero for all scores. After switching to the folder with the unzipped Performance Test files, I'm entering ./pt_linux_x64, which gives the results shown in the screen print.

    Windows 10 x64 2H21 and Ubuntu 20.04 have all updates applied, although it's possible that there are additional packages I need to install. All drivers and the latest BIOS are installed, too, so everything I know about is up to date.
    Mike

  • #2
    I found the command line options and tried -d 3 and -debug, with the same zero scores and the following in the log file:

    1473.738447: PerformanceTest Version: 10.2.1000
    1473.740479: Detect Model
    1473.741533:
    1473.742482: Detect CPU Name
    1473.745209: 12th Gen Intel(R) Core(TM) i7-12700KF
    1473.746159: Detect Manufacturer
    1473.748971: GenuineIntel
    1473.749773: Detect OS
    1473.750804: Ubuntu 20.04.3 LTS
    1473.751761: Detect Kernel
    1473.752589: 5.10.16.3-microsoft-standard-WSL2
    1473.753527: Detect Architecture
    1473.756587: x86_64
    1473.757412: Detect Memory
    1473.758404: 13215121408
    1473.759348: Detect CPU Frequency
    1473.762189: 3609
    1473.762992: Detect cpu sockets
    1473.765165: 1
    1473.765745: Detect cpu cores
    1473.767945: 10
    Mike

    Comment


    • #3
      It looks like the tests haven't been run yet, potentially the commands are being cut off in the terminal and not displayed.

      You can starts the tests by hitting the "A" key or you can launch "./pt_linux_x6 -r 3" to auto run all the tests (-r 1 for just CPU and -r 2 for just memory).

      Comment


      • #4
        When I tried adding -r 3 to the command line, the test ran and wrote results to results_all.yml. The results screen in Ubunto disappeared as soon as the last test finished, but this is what is in the results file.

        BaselineInfo:
        WebDBID: -1
        TimeStamp: 20220202032904
        Version:
        Major: 10
        Minor: 2
        Build: 1000
        SpecialBuildName: ""
        ptArchitecture: x86_64_linux
        Results:
        Results Complete: true
        NumTestProcesses: 20
        CPU_INTEGER_MATH: 120471.0392
        CPU_FLOATINGPOINT_MATH: 84583.160980130633
        CPU_PRIME: 90.367090923455891
        CPU_SORTING: 49498.785860053395
        CPU_ENCRYPTION: 27873.974361438566
        CPU_COMPRESSION: 470308.28903114225
        CPU_SINGLETHREAD: 4133.1558180260008
        CPU_PHYSICS: 1598.9261239353252
        CPU_MATRIX_MULT_SSE: 27335.597790764765
        CPU_mm: 3911.9003221987259
        CPU_sse: 14084.226804089065
        CPU_fma: 39280.124329501727
        CPU_avx: 28642.442238703519
        CPU_avx512: 0
        m_CPU_enc_SHA: 32405074702.264141
        m_CPU_enc_AES: 34590930773.690506
        m_CPU_enc_ECDSA: 20687936144.104755
        ME_ALLOC_S: 11025.579636576511
        ME_READ_S: 37339.419140625003
        ME_READ_L: 25150.6953125
        ME_WRITE: 17225.583984375
        ME_LARGE: 12243
        ME_LATENCY: 32.329993031785683
        ME_THREADED: 48112.55078125
        SUMM_CPU: 35149.064798523912
        SUMM_ME: 3816.2793285045354
        SystemInformation:
        OSName: Ubuntu 20.04.3 LTS
        Kernel: 5.10.16.3-microsoft-standard-WSL2
        Device: ""
        Processor: 12th Gen Intel(R) Core(TM) i7-12700KF
        NumSockets: 1
        Manufacturer: GenuineIntel
        NumCores: 10
        NumLogicals: 20
        CPUFrequency: 3609
        Memory: 12602
        MemModuleInfo:
        iNumMemSticks: 0
        Checksum: 46BD312C3D80F1A1BB74B27E3986CA31E761C0E3
        Mike

        Comment


        • #5
          Entering ''a" after the screen appeared worked, too, and the screen stayed in place after the tests finished. Thanks.
          Mike

          Comment


          • #6
            The screen was truncated. I didn't realize Windows Terminal wouldn't give any signs that the display was truncated.
            Mike

            Comment

            Working...
            X