-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance regression after updating to V8 11.3 #47350
Comments
This is definitely not a regression on the recent changes I've did to Ada branch. Reverting all of those changes still didn't make a difference. |
Comparing Node 19.8.1 with current main branch
|
/cc @nodejs/v8 @targos |
I'm waiting on merging this PR in order to understand it better: #47340 |
Once noticable change I saw on the V8 update is: we enabled turbofan compiler, and disabled 0d75c05#diff-d53f68b29a1c48c958c2e6779cc25c916a986357c6010dd01421c17adcf2f09bR282 |
Ada microbenchmarks still show the same result (295ns/iter) prior to V8 update, but the node benchmarks show bad results.
|
TurboFan has been enabled by default for years now ever since Crankshaft was removed. The addition of the |
cc @joyeecheung |
My local benchmarks show really bad results, but benchmark CI seems to persist with the current results. I'm closing this issue and open a new one if the situation happens again. CI: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1314/consoleText
|
I realized that after V8 11.3 the benchmarks changed a lot. As far as I know, Ada performs worse right now, and I'm researching the root cause of this.
Prior to V8 here is the benchmark CI result of Ada: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1307/
Comparing main branch before V8 11.3 merging with Ada branch (with V8 11.3)
Comparing current main branch with Ada branch (both on V8 11.3)
cc @targos @nodejs/performance
The text was updated successfully, but these errors were encountered: