Version
v18.16.0
Platform
Microsoft Windows NT 10.0.19045.0 x64
Subsystem
crypto
What steps will reproduce the bug?
const crypto = require('crypto');
const ts = Date.now();
crypto.pbkdf2Sync('XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', 'XXXXXXXXXXXXXXXXXXXXXXXXXXX', 100000, 32, 'sha512');
console.log(Date.now() - ts);
How often does it reproduce? Is there a required condition?
The code snippet in varying platforms logs lower numbers when ran on Node.js 14 & 16 (better) comparatively to Node.js 18 & 20 (worse).
Examples:
Windows 10
node 14/16: 70
node 18/20: 99
Ubuntu 20
node 14/16: 177
node 18/20: 240
And I've encountered similar results on Ubuntu 22, Debian 11, etc...
What is the expected behavior? Why is that the expected behavior?
I would expect no performance regression.
What do you see instead?
Performance regression ranging from ~30% to ~40%
Additional information
No response
Version
v18.16.0
Platform
Microsoft Windows NT 10.0.19045.0 x64
Subsystem
crypto
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
The code snippet in varying platforms logs lower numbers when ran on Node.js 14 & 16 (better) comparatively to Node.js 18 & 20 (worse).
Examples:
Windows 10
Ubuntu 20
And I've encountered similar results on Ubuntu 22, Debian 11, etc...
What is the expected behavior? Why is that the expected behavior?
I would expect no performance regression.
What do you see instead?
Performance regression ranging from ~30% to ~40%
Additional information
No response