BAD Benchmark Results for Node.JS Master 2017-06-13

Results for project Node.js master, build date 2017-06-13 23:39:35-07:00

  • commit: 9dc3f93
  • previous commit: 27cc30a
  • revision date: 2017-06-13 15:32:26-07:00
  • environment: Haswell-EP
    • cpu: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2×18 cores, stepping 2, LLC 45MB
    • mem: 128GB
    • os: Ubuntu Server 14.04 LTS
    • kernel: 3.19.0-25-generic

Baseline results were generated using release v4.2.2, with hash bcf6ac1 from 2015-11-03 19:49:06+00:00

benchmark relative std_dev* change since last run change since baseline change with PGO since baseline
😐 acmeair 0.17% -0.21% 43.94% 42.34%
😐 employeedb 0.57% -0.03% 18.51% 18.94%
😐 buffers/dataview-set.js 0.32% 0.62% 317.77% 317.01%
😐 word-finder 0.16% -0.04% 2.54% 2.59%
🙁 nodejs-mud 2.10% -1.23% 0.25% -1.20%

* Relative Standard Deviation (Standard Deviation/Average)

Subject Label Legend:
Attributes are determined based on the performance evolution of the workloads compared to the previous measurement iteration.
NEUTRAL: performance did not change by more than 1% for any workload
GOOD: performance improved by more than 1% for at least one workload and there is no regression greater than 1%
BAD: performance dropped by more than 1% for at least one workload and there is no improvement greater than 1%
UGLY: performance improved by more than 1% for at least one workload and also dropped by more than 1% for at least one workload

Our lab does a nightly source pull and build of the Node project and measures performance changes against the previous stable version and the previous nightly measurement. This is provided as a service to the community so that quality issues with current hardware can be identified quickly.

Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration.