-
Notifications
You must be signed in to change notification settings - Fork 438
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
feat: improve performance of response data parsing #1580
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arthurschreiber
force-pushed
the
arthur/rewrite-parser
branch
from
October 5, 2023 09:01
550e984
to
bacd841
Compare
@mShan0 @MichaelSun90 As discussed, here's the changes I have so far. Would you mind taking this over? |
arthurschreiber
commented
Oct 5, 2023
arthurschreiber
commented
Oct 5, 2023
arthurschreiber
commented
Oct 5, 2023
Co-authored-by: mShan0 <[email protected]> Co-authored-by: Arthur Schreiber <[email protected]>
arthurschreiber
commented
Oct 12, 2023
…tedious into arthur/rewrite-parser
Codecov Report
@@ Coverage Diff @@
## master #1580 +/- ##
==========================================
- Coverage 80.67% 78.24% -2.44%
==========================================
Files 92 93 +1
Lines 4709 4821 +112
Branches 871 921 +50
==========================================
- Hits 3799 3772 -27
- Misses 633 750 +117
- Partials 277 299 +22
|
arthurschreiber
commented
Oct 14, 2023
arthurschreiber
commented
Oct 14, 2023
arthurschreiber
commented
Oct 14, 2023
arthurschreiber
commented
Oct 14, 2023
arthurschreiber
commented
Oct 17, 2023
arthurschreiber
commented
Oct 18, 2023
arthurschreiber
changed the title
[WIP] synchronous chunk based token parser
feat: improve performance of response data parsing
Oct 21, 2023
🎉 This PR is included in version 16.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This replaces the current token parsing code (including value and metadata parsers) to use the "try parsing a single token, fail if not enough data is buffered, retry once more data comes in" approach described over in #1499 (comment).
TODOs
parser.streamBuffer.waitForData
NBCROW
token parsing.buf: Buffer | BufferList
type to onlybuf: Buffer
, I don't think we ever pass aBufferList
object here.Result
to be a proper class? So we can doreturn Result(value, offset)
. Probably should be benchmarked to see if it makes any difference.Results
On benchmarks that measure the full request-response cycle (like the
select-many-rows.js
benchmark), we can see an improvement ranging between a few percent up to 50% increase in iterations per second. Actual numbers will vary depending on various variables.Here are example benchmark results from my machine:
Node.js v16.20.0
master
branchNode.js v16.20.0
arthur/rewrite-parser
branch