Repository navigation
perf: prefetch kernel batches for async statement handles #578
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
Closed
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
b1daa65
perf: pipeline kernel result batch fetching
vuanhphung f32bcaf
fix: restrict kernel prefetch to async result handles
vuanhphung 8b8ffe4
docs: update kernel prefetch note after live validation
vuanhphung 9bc4047
fix: serialize kernel priming and dispose abandoned prefetches
vuanhphung 1434032
test: require a sustained CloudFetch wait before lifecycle checks
vuanhphung 062ae68
fix: preserve kernel results when close fails
vuanhphung File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🟡 Medium — When two
prime()calls overlap (for examplehasMore()andfetchNext()called together, or twofetchChunkcalls with no upstream lock — I found no fetch mutex inlib/), both await the samethis.inflightpromise. The first continuation setsinflight = undefinedand, with prefetch on, callsstartFetch(), which assigns a new promise P2. The second continuation then runsthis.inflight = undefinedwithout checking whether the field still holds the promise it awaited. That overwrites P2, and its ownstartFetch()starts P3. P2's batch is then lost: no caller ever reads it, so a result batch is silently dropped. Before this PR, each concurrent call made its ownfetchNextBatch()and no batch was lost.Fix: only clear the field if it still holds the promise this call awaited, e.g.
const current = this.inflight!; const settled = await current; if (this.inflight === current) this.inflight = undefined;. Add a unit test that callshasMore()andfetchNext()concurrently with prefetch enabled.