feat: add multi-target bandwidth measurements - #154
Open
andre-j3sus wants to merge 3 commits into
Open
Conversation
|
LGTM! |
andre-j3sus
commented
Aug 28, 2026
andre-j3sus
marked this pull request as ready for review
September 1, 2026 16:12
Collaborator
Author
|
/bonk |
|
Adds target-based request distribution, experimental per-step parallel bandwidth execution, aggregate result reporting, and per-request logging. Posted 1 inline correctness finding. Checks: |
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.
Adds measurementTargets as the origin-based contract for latency, download, and upload distribution. Existing full download and upload URLs remain as deprecated fallbacks when no targets are configured. Sequential and parallel requests use randomized-start target ordering, preserving duplicate targets.
Bandwidth steps can opt into experimental parallel execution through the TypeScript API. Parallel steps maintain one continuously replenished lane per selected target, keep count as the total physical request count, and report one aggregate point spanning the complete step. Aggregate duration excludes overlapping server-processing adjustments and paused intervals. Per-request logging remains physical-request based, while session metadata records the configured target count only when parallel execution is enabled.