Announcement

Collapse
No announcement yet.

How to benchmark several systems

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

  • How to benchmark several systems

    I have several systems that I want to benchmark. They share the same home directory which is on a NFS disk. So, I have ~/phoronix-test-suite and ~/.phoronix-test-suite which is the same actual directory for all systems.

    When I run the tests on one system, I move to a second and then third...

    The issue is that sometimes, even if I am on a new system, it still detects the old system's hardware. Even if I would run ./phoronix-test-suite system-info, it is showing me some of the previous system's info. Ho can I go round this? How I am supposed to test multiple systems?

  • #2
    Originally posted by trifud View Post
    I have several systems that I want to benchmark. They share the same home directory which is on a NFS disk. So, I have ~/phoronix-test-suite and ~/.phoronix-test-suite which is the same actual directory for all systems.

    When I run the tests on one system, I move to a second and then third...

    The issue is that sometimes, even if I am on a new system, it still detects the old system's hardware. Even if I would run ./phoronix-test-suite system-info, it is showing me some of the previous system's info. Ho can I go round this? How I am supposed to test multiple systems?
    PTS should never show an old system's hardware information.... Is the root file-system shared or somehow reporting the same/increasing uptime? Is the same CPU model being used on the different systems?

    If you set environment variable NO_PHODEVI_CACHE=1 does it all work as intended?
    Michael Larabel
    http://www.michaellarabel.com/

    Comment


    • #3
      I scratched ~/.phoronix-test-suite. Then, on a system with 2 x Intel Xeon Gold 6132 @ 2.60GHz I ran some tests. Only the /home/<username> is shared. Then, on the second system, which has 2 x Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz I run ./phoronix-test-suite system-info and I get the previous system's info:

      Code:
      [user@host ~/phoronix-test-suite]$ grep "model name" /proc/cpuinfo | uniq
      model name    : Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
      [user@host ~/phoronix-test-suite]$ ./phoronix-test-suite system-info
      
      Phoronix Test Suite v7.6.0m1
      System Information
      
      
        PROCESSOR:          2 x Intel Xeon Gold 6132 @ 2.60GHz
          Core Count:       12
          Thread Count:     24
          Extensions:       SSE 4.2 + AVX + RDRAND + FSGSBASE
          Cache Size:       19712 KB
          Microcode:        0x2000026
          Scaling Driver:   intel_pstate powersave
      
        GRAPHICS:           mgadrmfb
          Display Driver:   modesetting 1.19.3
          Monitor:          Smart Cable
      
        MOTHERBOARD:        Dell 008R9M
          Memory:           193536MB
          Chipset:          Intel Device 2020
          Network:          Broadcom Limited NetXtreme BCM5720 Gigabit PCIe
      
        DISK:               299GB PERC H740P Mini
          File-System:      nfs
          Mount Options:    data=ordered relatime rw seclabel
          Disk Scheduler:   DEADLINE
      
        OPERATING SYSTEM:   CentOS Linux 7
          Kernel:           3.10.0-693.5.2.el7.x86_64 (x86_64)
          Desktop:          GNOME Shell 3.22.3
          Compiler:         GCC 4.8.5 20150623

      Comment


      • #4
        PS I have tested on systems which don't share anything. I ran the tests on one system, then scp-ed the Phoronix folder to the other - same problem - it reports the first system's info.

        NO_PHODEVI_CACHE=1 does work.

        Comment


        • #5
          Hmm, the CPU model should never be cached past the termination of the phoronix test suite process, and if it changes, to then wipe the entire cache of system information... Will take a look.

          So if setting PHODEVI_NO_CACHE=1 does it behave as expected?
          Michael Larabel
          http://www.michaellarabel.com/

          Comment


          • #6
            Originally posted by Michael View Post
            Hmm, the CPU model should never be cached past the termination of the phoronix test suite process, and if it changes, to then wipe the entire cache of system information... Will take a look.

            So if setting PHODEVI_NO_CACHE=1 does it behave as expected?
            Yes, PHODEVI_NO_CACHE=1 solves it for me - I get the correct system info when I set this env variable.

            Comment


            • #7
              Originally posted by trifud View Post

              Yes, PHODEVI_NO_CACHE=1 solves it for me - I get the correct system info when I set this env variable.
              Okay, will investigate what's going on. Can you confirm whether the uptime on this second system is longer than the uptime on the first system?
              Michael Larabel
              http://www.michaellarabel.com/

              Comment


              • #8
                First system: 6:00
                Second system: 2:44
                Third system: 7 days, 6:26

                The first system's info appears on the second and third system.

                Comment

                Working...
                X