-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
buffer: improve byteLength performance #58048
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
base: main
Are you sure you want to change the base?
Conversation
32ec624
to
61ada9c
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #58048 +/- ##
==========================================
+ Coverage 90.18% 90.19% +0.01%
==========================================
Files 630 630
Lines 186393 186400 +7
Branches 36595 36601 +6
==========================================
+ Hits 168103 168131 +28
+ Misses 11090 11086 -4
+ Partials 7200 7183 -17
🚀 New features to boost your workflow:
|
This comment was marked as outdated.
This comment was marked as outdated.
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.
Looks like some pretty bad performance regressions.
61ada9c
to
e199141
Compare
# Conflicts: # src/node_external_reference.h
e199141
to
5bf5393
Compare
The results are in
|
From those results it appears like mostly a wash in terms of perf improvement but the change still looks worthwhile to me. |
cc @ronag |
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
This improves the performance for non one-byte strings.
Benchmark CI: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1705/