-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
stream: improve readable push performance #13113
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with CI green.
When CITGM is restored, a CITGM run would be highly welcomed. |
22eade4
to
89aa63b
Compare
There does not seem to be any CITGM failures caused by this particular PR. |
@mscdex great news, LGTM! |
89aa63b
to
b94a7e0
Compare
Landed in 359ea2a |
PR-URL: #13113 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
PR-URL: #13113 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
PR-URL: #13113 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
Should this be backported? Letting it bake for a little bit if so |
I'm 👍 on waiting, but it can be backported. |
This is mostly about improving performance when pushing strings, but pushing Buffers seems to be just a tad faster too. Specifically this PR makes two types of changes: avoid unnecessary chunk validation and reducing duplicated conditionals.
Here are results from one of the benchmark files I modified to be able to test strings:
CI: https://ci.nodejs.org/job/node-test-pull-request/8170/
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)