-
-
Notifications
You must be signed in to change notification settings - Fork 32.7k
Closed
Labels
benchmarkIssues and PRs related to the benchmark subsystem.Issues and PRs related to the benchmark subsystem.performanceIssues and PRs related to the performance of Node.js.Issues and PRs related to the performance of Node.js.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.
Description
- Version: 8.0
- Platform: Windows 7 x64
- Subsystem: v8, benchmark
This commit in the v8/node/vee-eight-lkgr
has turned the new Ignition+TurboFan pipeline on by default. To see the performance impact, I've built vee-eight-lkgr
before and after this commit and have started common Node.js benchmark suites with them.
Both builds have these same versions:
{ http_parser: '2.7.0',
node: '8.0.0-pre',
v8: '5.9.0 (candidate)',
uv: '1.11.0',
zlib: '1.2.11',
ares: '1.10.1-DEV',
modules: '56',
openssl: '1.0.2k',
icu: '58.2',
unicode: '9.0',
cldr: '30.0.3',
tz: '2016j' }
As my machine is not a fast one, I will post the results piecemeal.
UPD. All suites are complete.
TOC:
- arrays (+ fixed benchmarks)
- assert
- buffers (+
buffer-swap.js
with--set n=1e6
) - child_process
- crypto
- dgram
- domain
- es (+ new
foreach-bench.js
) - events
- fs
- http
- misc
- module
- net (except
tcp-raw-pipe.js
) - os
- path
- process
- querystring
- streams (+ on Windows)
- string_decoder
- timers (+ on Windows)
- tls
- url
- util
- vm (+ on Windows)
TimothyGu, egoroof, bricss, jorangreef, outsideris and 10 more
Metadata
Metadata
Assignees
Labels
benchmarkIssues and PRs related to the benchmark subsystem.Issues and PRs related to the benchmark subsystem.performanceIssues and PRs related to the performance of Node.js.Issues and PRs related to the performance of Node.js.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.