| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
@nodejs/v8 can you please have a look at this? It seems rather odd that the performance difference exists here.
Sorry, something went wrong.
|
Nit: @Septa2112 could you please update the commit message body's to include the "PR-URL"? That way the linter won't complain anymore 😃 |
Sorry, something went wrong.
Sorry, something went wrong.
Thanks for your suggestion. But according to my understanding, the "PR-URL" will only be generated when my commit is merged into the main branch. And I just referred to this PR #50621. Maybe the "Refs" should not be changed to "PR-URL"? So is it better to delete this PR-URL line in my commit message? Or change the PR link to a related issue link? Just like Refs: https://github.com/nodejs/node/issues/50620. |
Sorry, something went wrong.
|
Refs: is correct |
Sorry, something went wrong.
|
Sorry, I meant to add that part. I misread the number and it can be added later on. |
Sorry, something went wrong.
Improve performance of areSimilarFloatArrays by using primordial. Refs: nodejs#50621
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Improve performance of areSimilarFloatArrays by using primordial.
How find the issue
When I test performance between node-16.x and node-22-pre, I found performance regression in benchmark/assert/deepequal-typedarrays.js. Old binary is node-16.x and the new is node-22-pre
Original result of node-16.x and node-22-pre
How solved
I found the case benchmark/assert/deepequal-typedarrays.js will finally call function areSimilarFloatArrays(a, b) in lib/internal/util when strict=0 type='Float32Array'. The problem is similar with #50620. So I learned from the approach in #50621.
Results
Comparison between node_16.x and node-22-pre
I modified the code in main branch (v22.0.0-pre), and compare with node_16.x
Performance improvement on main(node-22-pre)
After the change, test on the latest main branch and get the results of performance comparison of node_22 before and after modifying the code.
Refs: #50621