fix beacon chain download speed - #2970
Merged
Merged
Conversation
sparrowDom
requested review from
clement-ux,
naddison36 and
shahthepro
as code owners
August 10, 2026 15:17
shahthepro
approved these changes
Aug 10, 2026
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
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.
Node's fetch defaults to
accept-encoding: gzip, deflate, which makes Lighthouse gzip the ~330MB state and drop content-length. Inflating that on the main thread backpressures the socket down to ~2 Mbps (a 15min download that hits the abort below), and the missing content-length also forces the slow chunk-accumulation path further down. Asking for identity doubles the wire bytes but the transfer takes ~2s.Code Change Checklist
To be completed before internal review begins:
Internal review: