This is a benchmark of the reference implementation of Graph500, an HPC benchmark focused on data intensive loads and commonly tested on supercomputers for complex data problems. Graph500 primarily stresses the communication subsystem of the hardware under test.
To run this test with the Phoronix Test Suite, the basic command is: phoronix-test-suite benchmark graph500.
* Uploading of benchmark result data to OpenBenchmarking.org is always optional (opt-in) via the Phoronix Test Suite for users wishing to share their results publicly. ** Data based on those opting to upload their test results to OpenBenchmarking.org and users enabling the opt-in anonymous statistics reporting while running benchmarks from an Internet-connected platform. Data updated weekly as of 29 November 2023.
pts/graph500-1.0.1 [View Source] Sat, 29 Jan 2022 11:06:02 GMT Add PROCS_PER_NODE_NOT_POWER_OF_TWO handling to detect otherwise the program fails to run for non power of 2 CPU core counts.
pts/graph500-1.0.0 [View Source] Fri, 28 Jan 2022 07:16:09 GMT Initial commit of Graph500, long overdue...
OpenBenchmarking.org metrics for this test profile configuration based on 556 public results since 28 January 2022 with the latest data as of 27 November 2023.
Below is an overview of the generalized performance for components where there is sufficient statistically significant data based upon user-uploaded results. It is important to keep in mind particularly in the Linux/open-source space there can be vastly different OS configurations, with this overview intended to offer just general guidance as to the performance expectations.
Based on OpenBenchmarking.org data, the selected test / test configuration (Graph500 3.0 - Scale: 26) has an average run-time of 19 minutes. By default this test profile is set to run at least 1 times but may increase if the standard deviation exceeds pre-defined defaults or other calculations deem additional runs necessary for greater statistical accuracy of the result.
Does It Scale Well With Increasing Cores?
Yes, based on the automated analysis of the collected public benchmark data, this test / test settings does generally scale well with increasing CPU core counts. Data based on publicly available results for this test / test settings, separated by vendor, result divided by the reference CPU clock speed, grouped by matching physical CPU core count, and normalized against the smallest core count tested from each vendor for each CPU having a sufficient number of test samples and statistically significant data.
Notable Instruction Set Usage
Notable instruction set extensions supported by this test, based on an automatic analysis by the Phoronix Test Suite / OpenBenchmarking.org analytics engine.
Requires passing a supported compiler/build flag (verified with targets: sandybridge, skylake, tigerlake, cascadelake, sapphirerapids, alderlake, znver2, znver3). Found on Intel processors since Sandy Bridge (2011). Found on AMD processors since Bulldozer (2011).
Requires passing a supported compiler/build flag (verified with targets: skylake, tigerlake, cascadelake, sapphirerapids, alderlake, znver2, znver3). Found on Intel processors since Haswell (2013). Found on AMD processors since Excavator (2016).
Requires passing a supported compiler/build flag (verified with targets: skylake, tigerlake, cascadelake, sapphirerapids, alderlake, znver2, znver3). Found on Intel processors since Haswell (2013). Found on AMD processors since Bulldozer (2011).
Advanced Vector Extensions 512 (AVX512)
Requires passing a supported compiler/build flag (verified with targets: cascadelake, sapphirerapids).
(ZMM REGISTER USE)
The test / benchmark does honor compiler flag changes.
Last automated analysis: 29 January 2022
This test profile binary relies on the shared libraries libm.so.6, libmpi.so.40, libc.so.6, libopen-rte.so.40, libopen-pal.so.40, libhwloc.so.15, libz.so.1, libudev.so.1.
Tested CPU Architectures
This benchmark has been successfully tested on the below mentioned architectures. The CPU architectures listed is where successful OpenBenchmarking.org result uploads occurred, namely for helping to determine if a given test is compatible with various alternative CPU architectures.