Intel Xeon testing with a Google Compute Engine c2-standard-8 and Google Array on Microsoft Windows Server 2022 Datacenter Build 20348 via the Phoronix Test Suite.
Processor: Intel Xeon @ 3.10GHz (4 Cores / 8 Threads), Motherboard: Google Compute Engine c2-standard-8, Memory: 2 x 16384 MB, Disk: 400GB Google PersistentDisk Disk, Graphics: Google Array
OS: Microsoft Windows Server 2022 Datacenter Build 20348, Kernel: 10.0.20348.1787 (x86_64), Display Driver: 1.1.4.28, File-System: NTFS, Screen Resolution: 1920x1080
Security Notes: __user pointer sanitization: Disabled + IBRS: Enabled + STIBP: Enabled + KPTI Enabled: Yes + VBS: Disabled
This is a test of t-test1 for basic memory allocator benchmarks. Note this test profile is currently very basic and the overall time does include the warmup time of the custom t-test1 compilation. Improvements welcome. Learn more via the OpenBenchmarking.org test page.
Threads: 2
Google PersistentDisk Disk: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: ./t-test1: line 7: ./t-test1_bin: No such file or directory
This is a performance test of CacheBench, which is part of LLCbench. CacheBench is designed to test the memory and cache bandwidth performance Learn more via the OpenBenchmarking.org test page.
Test: Read
Google PersistentDisk Disk: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./cachebench: line 3: ./cachebench: No such file or directory
Intel Memory Latency Checker (MLC) is a binary-only system memory bandwidth and latency benchmark. If the download fails you may need to manually download the file from https://www.intel.com/content/www/us/en/developer/articles/tool/intelr-memory-latency-checker.html and place it in your PTS download cache. On some systems root privileges are needed to run the MLC tester. Learn more via the OpenBenchmarking.org test page.
The IOzone benchmark tests the hard disk drive / file-system performance. Learn more via the OpenBenchmarking.org test page.
This is a test of t-test1 for basic memory allocator benchmarks. Note this test profile is currently very basic and the overall time does include the warmup time of the custom t-test1 compilation. Improvements welcome. Learn more via the OpenBenchmarking.org test page.
Threads: 1
Google PersistentDisk Disk: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: ./t-test1: line 7: ./t-test1_bin: No such file or directory
Intel Memory Latency Checker (MLC) is a binary-only system memory bandwidth and latency benchmark. If the download fails you may need to manually download the file from https://www.intel.com/content/www/us/en/developer/articles/tool/intelr-memory-latency-checker.html and place it in your PTS download cache. On some systems root privileges are needed to run the MLC tester. Learn more via the OpenBenchmarking.org test page.
This is a performance test of CacheBench, which is part of LLCbench. CacheBench is designed to test the memory and cache bandwidth performance Learn more via the OpenBenchmarking.org test page.
Test: Write
Google PersistentDisk Disk: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./cachebench: line 3: ./cachebench: No such file or directory
Test: Read / Modify / Write
Google PersistentDisk Disk: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./cachebench: line 3: ./cachebench: No such file or directory
Intel Memory Latency Checker (MLC) is a binary-only system memory bandwidth and latency benchmark. If the download fails you may need to manually download the file from https://www.intel.com/content/www/us/en/developer/articles/tool/intelr-memory-latency-checker.html and place it in your PTS download cache. On some systems root privileges are needed to run the MLC tester. Learn more via the OpenBenchmarking.org test page.
OSBench is a collection of micro-benchmarks for measuring operating system primitives like time to create threads/processes, launching programs, creating files, and memory allocation. Learn more via the OpenBenchmarking.org test page.
This is a test of EEMBC CoreMark processor benchmark. Learn more via the OpenBenchmarking.org test page.
Google PersistentDisk Disk: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: ./coremark: line 3: ./coremark.exe: No such file or directory
Intel Memory Latency Checker (MLC) is a binary-only system memory bandwidth and latency benchmark. If the download fails you may need to manually download the file from https://www.intel.com/content/www/us/en/developer/articles/tool/intelr-memory-latency-checker.html and place it in your PTS download cache. On some systems root privileges are needed to run the MLC tester. Learn more via the OpenBenchmarking.org test page.
This test measures the time needed to carry out some sample Git operations on an example, static repository that happens to be a copy of the GNOME GTK tool-kit repository. Learn more via the OpenBenchmarking.org test page.
Processor: Intel Xeon @ 3.10GHz (4 Cores / 8 Threads), Motherboard: Google Compute Engine c2-standard-8, Memory: 2 x 16384 MB, Disk: 400GB Google PersistentDisk Disk, Graphics: Google Array
OS: Microsoft Windows Server 2022 Datacenter Build 20348, Kernel: 10.0.20348.1787 (x86_64), Display Driver: 1.1.4.28, File-System: NTFS, Screen Resolution: 1920x1080
Security Notes: __user pointer sanitization: Disabled + IBRS: Enabled + STIBP: Enabled + KPTI Enabled: Yes + VBS: Disabled
Testing initiated at 10 June 2024 16:28 by user florin_barbu.