You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we use this package for our profiler-server repository. After upgrading the node version from v16 to v18, we observed ~30% performance regression. And after some investigation we realized that it's because of the createPublicKey and createPrivateKey calls that happen here:
I also filed an issue on nodejs for the regression on those APIs. For more context, please see it here: nodejs/node#50386
I was wondering if we can reduce the calls to these APIs in this repository with some caching mechanism maybe? I'm not sure as I'm not familiar with the code here. Wanted to ask to see if you have any ideas, thanks!
Version of this library used: 9.0.2
The text was updated successfully, but these errors were encountered:
Hi, we use this package for our profiler-server repository. After upgrading the node version from v16 to v18, we observed ~30% performance regression. And after some investigation we realized that it's because of the
createPublicKey
andcreatePrivateKey
calls that happen here:node-jsonwebtoken/verify.js
Lines 122 to 125 in bc28861
I also filed an issue on nodejs for the regression on those APIs. For more context, please see it here: nodejs/node#50386
I was wondering if we can reduce the calls to these APIs in this repository with some caching mechanism maybe? I'm not sure as I'm not familiar with the code here. Wanted to ask to see if you have any ideas, thanks!
Version of this library used: 9.0.2
The text was updated successfully, but these errors were encountered: