This test profile times how long it takes to build/compile Node.js itself from source. Node.js is a JavaScript run-time built from the Chrome V8 JavaScript engine while itself is written in C/C++.
To run this test with the Phoronix Test Suite, the basic command is: phoronix-test-suite benchmark build-nodejs.
OpenBenchmarking.org metrics for this test profile configuration based on 237 public results since 17 March 2021 with the latest data as of 14 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 (Timed Node.js Compilation 15.11 - Time To Compile) has an average run-time of 29 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.
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.
1 System - 68 Benchmark Results |
AMD Ryzen 7 4800H - TUXEDO s PULSE1501 - AMD Renoir Root Complex Arch rolling - 5.11.13-arch1-1 - X Server 1.20.10 |
1 System - 111 Benchmark Results |
2 x AMD EPYC 7V13 64-Core - Microsoft Virtual Machine - 442GB CentOS Linux 8 - 4.18.0-147.8.1.el8_1.x86_64 - GCC 8.3.1 20190507 |
2 Systems - 17 Benchmark Results |
AMD Ryzen 9 5950X 16-Core - Gigabyte B550I AORUS PRO AX - AMD Starship Ubuntu 20.04 - 5.11.13-051113-generic - GNOME Shell 3.36.7 |
1 System - 17 Benchmark Results |
AMD Ryzen 9 5950X 16-Core - Gigabyte B550I AORUS PRO AX - AMD Starship Ubuntu 20.04 - 5.11.13-051113-generic - GNOME Shell 3.36.7 |
3 Systems - 95 Benchmark Results |
2 x AMD EPYC 7V13 64-Core - Microsoft Virtual Machine - 442GB CentOS Linux 8 - 4.18.0-147.8.1.el8_1.x86_64 - GCC 8.3.1 20190507 |
2 Systems - 86 Benchmark Results |
2 x AMD EPYC 7V13 64-Core - Microsoft Virtual Machine - 442GB CentOS Linux 8 - 4.18.0-147.8.1.el8_1.x86_64 - GCC 8.3.1 20190507 |
1 System - 206 Benchmark Results |
2 x Intel $0000% - Supermicro X12DPi-N6 v1.00 - Intel Device 0998 CentOS Linux 8 - 4.18.0-80.el8.x86_64 - GCC 8.3.1 20191121 |
1 System - 197 Benchmark Results |
2 x Intel $0000% - Supermicro X12DPi-N6 v1.00 - Intel Device 0998 CentOS Linux 8 - 4.18.0-80.el8.x86_64 - GNOME Shell 3.28.3 |
1 System - 57 Benchmark Results |
AMD EPYC 7763 64-Core - Supermicro H12SSL-i v1.01 - AMD Starship Ubuntu 20.04 - 5.12.0-051200rc6daily20210408-generic - GNOME Shell 3.36.4 |
3 Systems - 189 Benchmark Results |
AMD EPYC 7763 64-Core - Supermicro H12SSL-i v1.01 - AMD Starship Ubuntu 20.04 - 5.12.0-051200rc6daily20210408-generic - GNOME Shell 3.36.4 |
1 System - 212 Benchmark Results |
Intel Core i5-8250U - LENOVO 20L7CTO1WW - Intel Xeon E3-1200 v6 Debian testing - 5.10.0-5-amd64 - GNOME Shell 3.38.4 |
3 Systems - 16 Benchmark Results |
AMD EPYC 7702 64-Core - ASRockRack EPYCD8 - AMD Starship Ubuntu 20.04 - 5.9.0-050900rc6daily20200921-generic - GNOME Shell 3.36.4 |