GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||
GeezerVison is showing github.com — src: add fast path to TextEncoder.encodeInto by anonrig · Pull Request #45701 · nodejs/node Conversation
|
|
Review requested:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/5027/ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-ppc64le,v8test=v8test/5027/ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I would be more inclined to accept this if the new capabilities were used by a subsequent commit. Otherwise the change doesn't bring anything to Node.js.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
@targos Should I include my changes depending on this to this particular pull request, and add |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
That would be fine, yes. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
These changes look fine to me. I'm approving, but I agree on what @targos said. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Nit: we already have so many files dealing with encodings, does this really need to be a new one (instead of, e.g., staying in node_buffer or maybe string_bytes)? And if so, is this the encoding file?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I don’t have any specific thoughts on this. I’ll try to move the encode utf8 to the node_encoding once this is implementation improves the existing benchmark.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I'm still not sure why this is a new file when it only covers a tiny part of all encoding-related routines.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-s390x,v8test=v8test/5040/ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=rhel8-ppc64le,v8test=v8test/5040/ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@tniessen Can you review this, since in your last review, you |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Anna Henningsen <[email protected]>
|
@targos If it's ok, I recommend creating a pull request for merging the v8 cherry-pick, and continue this performance experiment in this pull request. There are several new areas (wasm for example) that can leverage this cherry-pick. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| // For loop is required to trigger the fast path for encodeInto | ||
| // Since v8 fast path is only triggered when v8 optimization starts. |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
There is no guarantee that V8 would take the fast path.
| // For loop is required to trigger the fast path for encodeInto | |
| // Since v8 fast path is only triggered when v8 optimization starts. | |
| // Using a loop increases the chances of triggering the fast path for encodeInto | |
| // because V8 heuristically optimizes based on information gathered at runtime. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I'm still not sure why this is a new file when it only covers a tiny part of all encoding-related routines.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
There are git conflicts, no Jenkins CI run on the last commit, and two collaborators blocking the PR, removing
author ready
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks, @aduh95. Since other pull requests are merged, I’ll update this pull request only focusing on encodeInto. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.