* 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 current as of Fri, 09 Apr 2021 19:42:07 GMT.
pts/lammps-1.3.2 [View Source] Tue, 12 Jan 2021 10:27:58 GMT LAMMPS works fine on macOS.
pts/lammps-1.3.1 [View Source] Sun, 10 Jan 2021 20:50:23 GMT Update download mirror that is iffy.
pts/lammps-1.3.0 [View Source] Thu, 29 Oct 2020 10:11:23 GMT Update against LAMMPS 29Oct2020.
pts/lammps-1.2.1 [View Source] Fri, 18 Sep 2020 21:09:08 GMT Add back Rhodopsin Protein for those wanting the easier model.
pts/lammps-1.2.0 [View Source] Fri, 18 Sep 2020 20:40:07 GMT Update against LAMMPS 24Aug2020 latest release, also add more intense input file for working better on modern systems.
pts/lammps-1.1.0 [View Source] Fri, 10 Jan 2020 20:05:05 GMT Update against latest upstream lammps and other improvements to the script.
OpenBenchmarking.org metrics for this test profile configuration based on 1,035 public results since 29 October 2020 with the latest data as of 10 April 2021.
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 (LAMMPS Molecular Dynamics Simulator 29Oct2020 - Model: Rhodopsin Protein) has an average run-time of 2 minutes. By default this test profile is set to run at least 3 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.
Based on public OpenBenchmarking.org results, the selected test / test configuration has an average standard deviation of 2.3%.
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).