System info
Bluebird version: 3.4.7
Node.js version: 7.5.0
V8 version: 5.4.500.48
Plaform: Linux 4.8.13-100.fc23.x86_64 x64
CPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz × 8
Issue description
Bluebird with long stack traces is 15× slower in v7.5.0 than in v6.9.5 for doxbee sequential benchmark (on my PC, YMMV). It also impacts the Node app I work on (real-world usage) to the point I had to deactivate long stack traces in dev.
System info Bluebird version: 3.4.7 Node.js version: 7.5.0 V8 version: 5.4.500.48 Plaform: Linux 4.8.13-100.fc23.x86_64 x64 CPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz × 8
Issue description
Bluebird with long stack traces is 15× slower in v7.5.0 than in v6.9.5 for doxbee sequential benchmark (on my PC, YMMV). It also impacts the Node app I work on (real-world usage) to the point I had to deactivate long stack traces in dev.
It seems to be caused by a performance regression of Error.captureStackTrace in Node v7.x.
This issue's purpose is mainly documentation, because I don't see what could be done bluebird-wise to mitigate this.
Summary:
Full brenchmark outputs: