Timed Node.js Compilation

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.

Project Site

nodejs.org

Test Created

17 March 2021

Test Maintainer

Michael Larabel 

Test Type

Processor

Average Install Time

2 Seconds

Average Run Time

27 Minutes, 51 Seconds

Test Dependencies

C/C++ Compiler Toolchain + Python + OpenSSL

Accolades

5k+ Downloads

Supported Platforms


Public Result Uploads *Reported Installs **Reported Test Completions **Test Profile Page Views ***OpenBenchmarking.orgEventsTimed Node.js Compilation Popularity Statisticspts/build-nodejs2021.032021.042021.052021.062021.072021.082021.092021.106001200180024003000
* 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.
*** Test profile page view reporting began March 2021.
Data current as of 13 October 2021.

Revision History

pts/build-nodejs-1.0.0   [View Source]   Wed, 17 Mar 2021 12:54:33 GMT
Add Node.js timed compilation benchmark.

Suites Using This Test

Timed Code Compilation

Multi-Core

Programmer / Developer System Benchmarks


Performance Metrics

Analyze Test Configuration:

Timed Node.js Compilation 15.11

Time To Compile

OpenBenchmarking.org metrics for this test profile configuration based on 701 public results since 17 March 2021 with the latest data as of 16 October 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.

Component
Percentile Rank
# Compatible Public Results
Seconds (Average)
86th
16
108 +/- 5
Mid-Tier
75th
> 128
69th
30
140 +/- 10
63rd
16
169 +/- 7
62nd
3
173 +/- 9
60th
9
193 +/- 2
55th
3
228 +/- 11
Median
50th
243
37th
7
380 +/- 18
37th
10
381 +/- 22
35th
19
401 +/- 35
33rd
24
423 +/- 21
29th
6
465 +/- 1
Low-Tier
25th
> 581
25th
5
588 +/- 12
25th
4
592 +/- 59
24th
3
622 +/- 1
21st
3
757 +/- 4
18th
3
889 +/- 1
18th
3
890 +/- 1
17th
3
939 +/- 2
17th
3
992 +/- 5
16th
4
1017 +/- 1
15th
3
1090 +/- 2
14th
3
1103 +/- 10
14th
4
1106 +/- 1
12th
3
1216 +/- 1
12th
3
1255 +/- 3
11th
5
1266 +/- 3
10th
4
1321 +/- 8
9th
3
1329 +/- 2
9th
4
1331 +/- 4
9th
3
1356 +/- 2
8th
3
1377 +/- 2
8th
3
1489 +/- 1
7th
3
1506 +/- 19
7th
3
1506 +/- 1
6th
3
1550 +/- 1
6th
3
1578 +/- 4
5th
3
1750 +/- 35
4th
3
1800 +/- 2
2nd
3
3348 +/- 2
1st
3
4981 +/- 354
OpenBenchmarking.orgDistribution Of Public Results - Time To Compile690 Results Range From 66 To 7114 Seconds662073484896307719121053119413351476161717581899204021812322246326042745288630273168330934503591373238734014415542964437457847194860500151425283542455655706584759886129627064116552669368346975711660120180240300

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 18 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.

OpenBenchmarking.orgMinutesTime Required To Complete BenchmarkTime To CompileRun-Time20406080100Min: 1 / Avg: 17.84 / Max: 115

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.

AMDIntelOpenBenchmarking.orgRelative Core Scaling To BaseTimed Node.js Compilation CPU Core ScalingTime To Compile468121624324864510152025