node/benchmark/async_hooks
Anna Henningsen b14ce72353 benchmark: always throw the same Error instance
Stack trace capturing currently accounts for 40 % of the benchmark
running time. Always throwing the same exception object removes
that overhead and lets the benchmark be more focused on what it is
supposed to measure.

Refs: https://github.com/nodejs/node/pull/34512#issuecomment-663977271

PR-URL: https://github.com/nodejs/node/pull/34523
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Andrey Pechkurov <apechkurov@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Gerhard Stöbich <deb2001-github@yahoo.de>
2020-07-29 10:59:26 +03:00
..
async-resource-vs-destroy.js benchmark: fix async-resource benchmark 2020-06-06 17:36:52 +02:00
gc-tracking.js async_hooks: move to lazy destroy hook registration in AsyncResource 2020-04-06 16:14:43 +02:00
http-server.js
promises.js benchmark: always throw the same Error instance 2020-07-29 10:59:26 +03:00