feat: adaptive V2 reconstruction with split/grouped range strategy#692
Draft
XciD wants to merge 1 commit intofeat/v2-reconstruction-multirangefrom
Draft
feat: adaptive V2 reconstruction with split/grouped range strategy#692XciD wants to merge 1 commit intofeat/v2-reconstruction-multirangefrom
XciD wants to merge 1 commit intofeat/v2-reconstruction-multirangefrom
Conversation
Split large ranges (avg >= 256KB) into individual single-range HTTP requests for better CDN cache hit rates and parallelism. Keep small/fragmented ranges grouped in multi-range requests to avoid per-request overhead. Includes benchmark instrumentation for V1 vs V2 comparison.
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.
Summary
[BENCH]instrumentation (eprintln) for V1 vs V2 comparison: reconstruction timing, S3 response details, multipart parsingThis is the "V2-adaptive" approach from the benchmark results:
V2-adaptive is on par with V1 for non-fragmented files and 29% faster on highly fragmented ones.