Repository navigation
Conversation
…eads Reading crossref-demo/works v5.2.x, records.ndjson died with "Worker exceeded memory limit" wherever the next leaves were large, after sending its 200 and count header, so clients saw an empty stream. Leaves end at a key-hash boundary (mean 1,024 entries, up to 8,192): book-chapter's first leaf in v5.2.1 holds 6,920 records, about 80 MB of bodies, and iterate decoded whole leaves through bodyLines (cached in the LRU), four ahead. The stream also did all its work in start(), enqueueing regardless of how fast the client read. iterate takes `stream`: with payloads, each leaf is read through leafStream (gunzipped line by line, not cached), one leaf at a time. records.ndjson uses it and produces up to 512 lines or 1 MB per pull(). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reading crossref-demo/works v5.2.x, records.ndjson died with "Worker exceeded memory limit" wherever the next leaves were large, after sending its 200 and count header, so clients saw an empty stream. Leaves end at a key-hash boundary (mean 1,024 entries, up to 8,192): book-chapter's first leaf in v5.2.1 holds 6,920 records, about 80 MB of bodies, and iterate decoded whole leaves through bodyLines (cached in the LRU), four ahead. The stream also did all its work in start(), enqueueing regardless of how fast the client read.
iterate takes
stream: with payloads, each leaf is read through leafStream (gunzipped line by line, not cached), one leaf at a time. records.ndjson uses it and produces up to 512 lines or 1 MB per pull().