-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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 Writable.destroy performance #35067
Conversation
Avoid nextTick if there are no pending callbacks.
@nodejs/streams |
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
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
Feel free to add a comment that this condition is equivalent to no callbacks being pending :)
7588c63
to
ab7b73d
Compare
Commit Queue failed- Loading data for nodejs/node/pull/35067 ✔ Done loading data for nodejs/node/pull/35067 ----------------------------------- PR info ------------------------------------ Title stream: improve Writable.destroy performance (#35067) Author Robert Nagy (@ronag) Branch ronag:writable-destroy-perf -> nodejs:master Labels author ready, stream Commits 4 - stream: improbe Writable.destroy performance - fixup - fixup - fixup Committers 1 - Robert Nagy PR-URL: https://github.com/nodejs/node/pull/35067 Reviewed-By: Matteo Collina Reviewed-By: Anna Henningsen Reviewed-By: Luigi Pinca Reviewed-By: Ricky Zhou <[email protected]> ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/35067 Reviewed-By: Matteo Collina Reviewed-By: Anna Henningsen Reviewed-By: Luigi Pinca Reviewed-By: Ricky Zhou <[email protected]> -------------------------------------------------------------------------------- ⚠ Commits were pushed since the last review: ⚠ - fixup ⚠ - fixup ✖ Last GitHub CI failed ℹ Last Full PR CI on 2020-09-07T09:00:43Z: https://ci.nodejs.org/job/node-test-pull-request/33086/ - Querying data for job/node-test-pull-request/33086/ ✔ Build data downloaded ✔ Last Jenkins CI successful ℹ This PR was created on Sat, 05 Sep 2020 11:51:48 GMT ✔ Approvals: 4 ✔ - Matteo Collina (@mcollina) (TSC): https://github.com/nodejs/node/pull/35067#pullrequestreview-483051355 ✔ - Anna Henningsen (@addaleax): https://github.com/nodejs/node/pull/35067#pullrequestreview-483067062 ✔ - Luigi Pinca (@lpinca): https://github.com/nodejs/node/pull/35067#pullrequestreview-483072059 ✔ - Ricky Zhou (@rickyes): https://github.com/nodejs/node/pull/35067#pullrequestreview-483143528 -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu |
Commit Queue failed- Loading data for nodejs/node/pull/35067 ✔ Done loading data for nodejs/node/pull/35067 ----------------------------------- PR info ------------------------------------ Title stream: improve Writable.destroy performance (#35067) Author Robert Nagy (@ronag) Branch ronag:writable-destroy-perf -> nodejs:master Labels author ready, stream Commits 4 - stream: improbe Writable.destroy performance - fixup - fixup - fixup Committers 1 - Robert Nagy PR-URL: https://github.com/nodejs/node/pull/35067 Reviewed-By: Matteo Collina Reviewed-By: Anna Henningsen Reviewed-By: Luigi Pinca Reviewed-By: Ricky Zhou <[email protected]> ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/35067 Reviewed-By: Matteo Collina Reviewed-By: Anna Henningsen Reviewed-By: Luigi Pinca Reviewed-By: Ricky Zhou <[email protected]> -------------------------------------------------------------------------------- ✖ Last GitHub CI failed ℹ Last Full PR CI on 2020-09-07T14:21:04Z: https://ci.nodejs.org/job/node-test-pull-request/33086/ - Querying data for job/node-test-pull-request/33086/ ✔ Build data downloaded ✔ Last Jenkins CI successful ℹ This PR was created on Sat, 05 Sep 2020 11:51:48 GMT ✔ Approvals: 4 ✔ - Matteo Collina (@mcollina) (TSC): https://github.com/nodejs/node/pull/35067#pullrequestreview-483051355 ✔ - Anna Henningsen (@addaleax): https://github.com/nodejs/node/pull/35067#pullrequestreview-483593618 ✔ - Luigi Pinca (@lpinca): https://github.com/nodejs/node/pull/35067#pullrequestreview-483072059 ✔ - Ricky Zhou (@rickyes): https://github.com/nodejs/node/pull/35067#pullrequestreview-483143528 -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncu |
@nodejs/build a little trouble landing with the GH action? Something you want to take a look at or should I just land this manually? |
Avoid nextTick if there are no pending callbacks. PR-URL: nodejs#35067 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ricky Zhou <[email protected]>
Landed in e0d3b75 |
@ronag |
Sorry if I stomped all over the "land manually? change edit permissions? something else?" conversation by landing this. Wasn't my intention. I figured @ronag probably would prefer a resolution (landing) over some back-and-forth about this, but maybe I'm wrong. |
@Trott imo it should always be 100% ok to land over this particular X, just trying to figure out the forensics on the implication that it was unavoidable. |
this doesn't land cleanly on |
Avoid nextTick if there are no pending callbacks. PR-URL: nodejs#35067 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ricky Zhou <[email protected]>
Avoid nextTick if there are no pending callbacks.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes