Uh oh!
There was an error while loading. Please reload this page.
fs: improve error performance of writevSync - #50038
Conversation
IlyasShabi
commented
Oct 4, 2023
Feel free to suggest improvements in the benchmark file |
Uzlopak
commented
Oct 4, 2023
Afaik in c++ returning a value is slower than modifying a variable passed as parameter (by ref). |
There was a problem hiding this comment.
Please add an invalid type to benchmarks
There was a problem hiding this comment.
@anonrig I would appreciate help creating a good bench script for my first PR 🙏
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
In order to remove dead code elimination store the result of this operation and assert it when the benchmark finishes.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Did you swap the old and new node binary parameters when comparing the benchmarks or is that actually a 58% performance regression? |
Uh oh!
There was an error while loading. Please reload this page.
mscdex
commented
Oct 5, 2023
FWIW the changes currently result in: I'm guessing this should instead be more about improving the error case? |
There was a problem hiding this comment.
We don't need a try/catch on valid part
There was a problem hiding this comment.
This is not a file descriptor. The variable name suggests fd
nodejs-github-bot
commented
Oct 7, 2023
nodejs-github-bot
commented
Oct 8, 2023
nodejs-github-bot
commented
Oct 12, 2023
Landed in bf0f078 |
PR-URL: #50038 Refs: nodejs/performance#106 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
PR-URL: nodejs#50038 Refs: nodejs/performance#106 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Local benchmark:
Ref: nodejs/performance#106