Skip to content

Conversation

@anthony-tuininga
Copy link
Contributor

@anthony-tuiningaanthony-tuininga commented Mar 4, 2019

Improve performance creating strings using N-API by ensuring that the strings are not internalized (see Node issue #26437).

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@nodejs-github-botnodejs-github-bot added the c++ Issues and PRs that require attention from people who are familiar with C++. label Mar 4, 2019
Copy link
Member

@addaleaxaddaleax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@addaleaxaddaleax added the node-api Issues and PRs related to the Node-API. label Mar 4, 2019
@addaleax
Copy link
Member

CI: https://ci.nodejs.org/job/node-test-pull-request/21197/

(Travis is going to complain about the commit message, but you can ignore that, it’s information for the person who lands the commit, not necessarily the author.)

@mhdawson
Copy link
Member

This seems to confirm the preference for kNormal as the safer default choice. https://groups.google.com/forum/#!topic/v8-users/xoqi4ee8x74

Copy link
Member

@mhdawsonmhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mhdawsonmhdawson added performance Issues and PRs related to the performance of Node.js. lts-watch-v8.x labels Mar 4, 2019
@mhdawson
Copy link
Member

@anthony-tuininga thanks for your work on this.

@anthony-tuininga
Copy link
ContributorAuthor

You're welcome. Thanks for the quick turnaround on the approvals! Would love to see this released in 8.x and 10.x as well so that our users won't see a performance hit when upgrading to the next version of our module (in which we hope to use N-API).

Let me know if you want me to add the checks in the other string creation methods yet or if that should be deferred for another issue and PR?

@addaleax
Copy link
Member

Let me know if you want me to add the checks in the other string creation methods yet or if that should be deferred for another issue and PR?

If it’s all the same to you, I’d rather do it now/here. :)

@anthony-tuininga
Copy link
ContributorAuthor

Ok. I'll add the checks here. One moment.

@mhdawson
Copy link
Member

@anthony-tuininga I agree with wanting to get this back to 10.x and 8.x if possible. I've already added the tags so that we consider doing that.

@anthony-tuininga
Copy link
ContributorAuthor

Great. Let me know if you need anything further from me.

@joyeecheung
Copy link
Member

@BridgeARBridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Mar 7, 2019
BridgeAR pushed a commit to BridgeAR/node that referenced this pull request Mar 8, 2019
Improve performance creating strings using N-API by ensuring that the strings are not internalized. Added test cases for latin-1 and utf-16 strings. PR-URL: nodejs#26439Fixes: nodejs#26437 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: James M Snell <[email protected]>
@BridgeAR
Copy link
Member

Landed in 914d908

@anthony-tuininga congratulations to your first commit to Node.js! 🎉

I fixed the commit message to adhere to our commit guidelines while landing.

@BridgeARBridgeAR closed this Mar 8, 2019
BridgeAR pushed a commit to BridgeAR/node that referenced this pull request Mar 13, 2019
Improve performance creating strings using N-API by ensuring that the strings are not internalized. Added test cases for latin-1 and utf-16 strings. PR-URL: nodejs#26439Fixes: nodejs#26437 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: James M Snell <[email protected]>
BridgeAR pushed a commit that referenced this pull request Mar 14, 2019
Improve performance creating strings using N-API by ensuring that the strings are not internalized. Added test cases for latin-1 and utf-16 strings. PR-URL: #26439Fixes: #26437 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: James M Snell <[email protected]>
@anthony-tuiningaanthony-tuininga mentioned this pull request Apr 3, 2019
MylesBorins pushed a commit that referenced this pull request Apr 5, 2019
Improve performance creating strings using N-API by ensuring that the strings are not internalized. Added test cases for latin-1 and utf-16 strings. PR-URL: #26439Fixes: #26437 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: James M Snell <[email protected]>
@MylesBorins
Copy link
Contributor

I've landed on 10.x and 8.x

MylesBorins pushed a commit that referenced this pull request Apr 5, 2019
Improve performance creating strings using N-API by ensuring that the strings are not internalized. Added test cases for latin-1 and utf-16 strings. PR-URL: #26439Fixes: #26437 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this pull request Apr 16, 2019
Improve performance creating strings using N-API by ensuring that the strings are not internalized. Added test cases for latin-1 and utf-16 strings. PR-URL: #26439Fixes: #26437 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: James M Snell <[email protected]>
@BethGriggsBethGriggs mentioned this pull request May 1, 2019
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.c++Issues and PRs that require attention from people who are familiar with C++.node-apiIssues and PRs related to the Node-API.performanceIssues and PRs related to the performance of Node.js.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

@anthony-tuininga@addaleax@mhdawson@joyeecheung@BridgeAR@MylesBorins@jasnell@nodejs-github-bot