A Node.js Express server with a Node-based loadtest client for facilitating HTTP benchmarking.
To run this test with the Phoronix Test Suite, the basic command is: phoronix-test-suite benchmark node-express-loadtest.
OpenBenchmarking.org metrics for this test profile configuration based on 3,835 public results since 1 October 2018 with the latest data as of 21 August 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 (Node.js Express HTTP Load Test) has an average run-time of 6 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.2%.
No, based on the automated analysis of the collected public benchmark data, this test / test settings does not 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.
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.
1 System - 41 Benchmark Results |
2 x AMD EPYC 7601 32-Core - Supermicro Super Server H11DSi v2.00 - AMD 17h Ubuntu 24.04 - 6.8.0-51-generic - GNOME Shell 46.0 |
||
1 System - 143 Benchmark Results |
Apple M4 Max - Apple MacBook Pro - 128GB macOS 15.1 - 24.1.0 - GCC 16.0.0 + Clang 16.0.0 |
||
10 Systems - 35 Benchmark Results |
4 x AMD EPYC 9354 32-Core - Intel 440BX - 32GB Ubuntu 20.04.4 LTS - 5.10.142-1.ph4-esx - GCC 9.4.0 |
||
12 Systems - 35 Benchmark Results |
32 x AMD EPYC 7351P 16-Core - Intel 440BX - 32GB Ubuntu 20.04.4 LTS - 5.10.142-1.ph4-esx - GCC 9.4.0 |
||
1 System - 529 Benchmark Results |
Intel Xeon Platinum 8375C - Amazon EC2 m6id.4xlarge - Intel 440FX 82441FX PMC Ubuntu 24.04 - 6.8.0-1009-aws - GCC 13.2.0 |
||
1 System - 529 Benchmark Results |
Intel Xeon Platinum 8375C - Amazon EC2 m6id.4xlarge - Intel 440FX 82441FX PMC Ubuntu 24.04 - 6.8.0-1009-aws - GCC 13.2.0 |
||
1 System - 529 Benchmark Results |
AMD EPYC 7R13 - Amazon EC2 m6a.4xlarge - Intel 440FX 82441FX PMC Ubuntu 24.04 - 6.8.0-1009-aws - GCC 13.2.0 |
||
1 System - 529 Benchmark Results |
AMD EPYC 7R13 - Amazon EC2 m6a.4xlarge - Intel 440FX 82441FX PMC Ubuntu 24.04 - 6.8.0-1009-aws - GCC 13.2.0 |
||
1 System - 529 Benchmark Results |
|
1 System - 529 Benchmark Results
| |