0
0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
nodejs/benchmark
Kenny Yuan e41ccd4e2d n-api: improve runtime perf of n-api func call
Added a new struct CallbackBundle to eliminate all
GetInternalField() calls.

The principle is to store all required data inside a C++ struct,
and then store the pointer in the JavaScript object. Before this
change, the required data are stored in the JavaScript object in
3 or 4 seperate pointers. For every napi fun call, 3 of them
have to be fetched out, which are 3 GetInternalField() calls;
after this change, the C++ struct will be directly fetched out
by using v8::External::Value(), which is faster.

Profiling data show that GetInternalField() is slow.
On an i7-4770K (3.50GHz) box, a C++ V8-binding fun call is 8 ns,
before this change, napi fun call is 36 ns; after this change,
napi fun call is 20 ns.

The above data are measured using a modified benchmark in
'benchmark/misc/function_call'. The modification adds an indicator
of the average time of a "chatty" napi fun call (max 50M runs).
This change will speed up chatty case 1.8x (overall), and will cut
down the delay of napi mechanism to approx. 0.5x.

Background: a simple C++ binding function (e.g. receiving little
from JS, doing little and returning little to JS) is called
'chatty' case for JS<-->C++ fun call routine.

This improvement also applies to getter/setter fun calls.

PR-URL: https://github.com/nodejs/node/pull/21072
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com>
2018-06-07 22:56:20 -04:00
..
arrays benchmark: do not multiply n by 1e6 in arrays 2018-04-22 11:06:40 +02:00
assert benchmark: refactor benchmark/assert/throws.js 2018-06-02 05:17:29 +02:00
async_hooks benchmark: refactor 2018-02-01 10:49:04 +01:00
buffers test: fix long-running buffer benchmarks 2018-04-22 11:06:30 +02:00
child_process benchmark: (child_process) use destructuring 2018-01-23 01:29:32 +01:00
cluster benchmark: use destructuring 2018-01-23 01:29:34 +01:00
crypto test: run crypto benchmark only once in tests 2018-06-02 04:42:09 +02:00
dgram benchmark: refactor 2018-02-01 10:49:04 +01:00
dns benchmark: use destructuring 2018-01-23 01:29:34 +01:00
domain benchmark: refactor 2018-02-01 10:49:04 +01:00
es benchmark: disable only the ESLint rule needing it 2018-06-06 21:03:32 -07:00
events events: optimize condition for optimal scenario 2018-05-03 14:45:09 +02:00
fixtures worker: rename to worker_threads 2018-06-06 19:44:15 +02:00
fs fs: drop duplicate API in promises mode 2018-05-19 11:04:28 +03:00
http http: refactor outgoing headers processing 2018-04-27 20:31:25 +02:00
http2 src: remove --expose-http2 option 2018-05-24 08:28:02 +02:00
misc n-api: improve runtime perf of n-api func call 2018-06-07 22:56:20 -04:00
module benchmark: changed millions and thousands to n 2018-04-10 00:22:33 +02:00
net src: refactor WriteWrap and ShutdownWraps 2018-02-14 10:00:29 +01:00
os benchmark: (os) use destructuring 2018-01-23 01:29:23 +01:00
path benchmark: fix platform in basename-win32 2018-02-01 10:48:56 +01:00
process benchmark: track exec time in next-tick-exec 2018-05-06 07:29:47 +02:00
querystring benchmark,lib,test,tools: use consistent quotes 2018-03-07 19:06:44 -08:00
streams benchmark: changed millions and thousands to n 2018-04-10 00:22:33 +02:00
string_decoder benchmark: (string_decoder) use destructuring 2018-01-23 01:29:25 +01:00
timers timers: use only a single TimerWrap instance 2018-05-22 23:26:12 +04:00
tls tls: move convertNPNProtocols to End-of-Life 2018-05-17 09:53:44 -07:00
url benchmark: fix benchmark for url 2018-03-11 03:56:17 +01:00
util lib: add internal PriorityQueue class 2018-05-22 23:24:37 +04:00
v8 benchmark: refactor 2018-02-01 10:49:04 +01:00
vm benchmark: refactor 2018-02-01 10:49:04 +01:00
worker worker: rename to worker_threads 2018-06-06 19:44:15 +02:00
zlib benchmark: add bench for zlib gzip + gunzip cycle 2018-04-28 08:32:12 +02:00
_benchmark_progress.js benchmark: var to const 2017-09-19 21:14:38 -03:00
_cli.js benchmark: improve cli error message 2017-04-17 14:48:40 -07:00
_cli.R
_http-benchmarkers.js benchmark: cut down http benchmark run time 2018-02-01 11:43:30 +01:00
_test-double-benchmarker.js benchmark: implement duration in http test double 2018-01-29 17:46:14 +08:00
common.js benchmark: remove needless RegExp capturing 2017-06-19 18:06:17 +03:00
compare.js benchmark: improve compare output 2018-02-08 11:38:25 -05:00
compare.R benchmark: fix "comparisons"' typo 2018-06-02 08:07:22 +09:00
README.md http2: add tests and benchmarks 2017-08-04 12:55:58 -07:00
run.js tools,benchmark: use stricter indentation linting 2017-06-27 06:17:06 -07:00
scatter.js tools,benchmark: use stricter indentation linting 2017-06-27 06:17:06 -07:00
scatter.R

Node.js Core Benchmarks

This folder contains code and data used to measure performance of different Node.js implementations and different ways of writing JavaScript run by the built-in JavaScript engine.

For a detailed guide on how to write and run benchmarks in this directory, see the guide on benchmarks.

Table of Contents

Benchmark Directories

Directory Purpose
arrays Benchmarks for various operations on array-like objects, including Array, Buffer, and typed arrays.
assert Benchmarks for the assert subsystem.
buffers Benchmarks for the buffer subsystem.
child_process Benchmarks for the child_process subsystem.
crypto Benchmarks for the crypto subsystem.
dgram Benchmarks for the dgram subsystem.
domain Benchmarks for the domain subsystem.
es Benchmarks for various new ECMAScript features and their pre-ES2015 counterparts.
events Benchmarks for the events subsystem.
fixtures Benchmarks fixtures used in various benchmarks throughout the benchmark suite.
fs Benchmarks for the fs subsystem.
http Benchmarks for the http subsystem.
http2 Benchmarks for the http2 subsystem.
misc Miscellaneous benchmarks and benchmarks for shared internal modules.
module Benchmarks for the module subsystem.
net Benchmarks for the net subsystem.
path Benchmarks for the path subsystem.
process Benchmarks for the process subsystem.
querystring Benchmarks for the querystring subsystem.
streams Benchmarks for the streams subsystem.
string_decoder Benchmarks for the string_decoder subsystem.
timers Benchmarks for the timers subsystem, including setTimeout, setInterval, .etc.
tls Benchmarks for the tls subsystem.
url Benchmarks for the url subsystem, including the legacy url implementation and the WHATWG URL implementation.
util Benchmarks for the util subsystem.
vm Benchmarks for the vm subsystem.

Other Top-level files

The top-level files include common dependencies of the benchmarks and the tools for launching benchmarks and visualizing their output. The actual benchmark scripts should be placed in their corresponding directories.

  • _benchmark_progress.js: implements the progress bar displayed when running compare.js
  • _cli.js: parses the command line arguments passed to compare.js, run.js and scatter.js
  • _cli.R: parses the command line arguments passed to compare.R
  • _http-benchmarkers.js: selects and runs external tools for benchmarking the http subsystem.
  • common.js: see Common API.
  • compare.js: command line tool for comparing performance between different Node.js binaries.
  • compare.R: R script for statistically analyzing the output of compare.js
  • run.js: command line tool for running individual benchmark suite(s).
  • scatter.js: command line tool for comparing the performance between different parameters in benchmark configurations, for example to analyze the time complexity.
  • scatter.R: R script for visualizing the output of scatter.js with scatter plots.

Common API

The common.js module is used by benchmarks for consistency across repeated tasks. It has a number of helpful functions and properties to help with writing benchmarks.

createBenchmark(fn, configs[, options])

See the guide on writing benchmarks.

default_http_benchmarker

The default benchmarker used to run HTTP benchmarks. See the guide on writing HTTP benchmarks.

PORT

The default port used to run HTTP benchmarks. See the guide on writing HTTP benchmarks.

sendResult(data)

Used in special benchmarks that can't use createBenchmark and the object it returns to accomplish what they need. This function reports timing data to the parent process (usually created by running compare.js, run.js or scatter.js).