fix: optimize WS file transfer with binary frames and larger chunks#482
Merged
Conversation
added 5 commits
May 8, 2026 15:15
This reverts commit d319269.
kevin-mcgoldrick
approved these changes
Jun 29, 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.
Summary
Fixes slow cross-region agent bootstrap by switching WebSocket file transfer chunks from base64 text frames to binary frames.
This reduces overhead during controller-to-agent bootstrap file delivery, especially for EAST controller -> WEST agent traffic, where bootstrap was taking ~4-5 minutes before this work. Also increases the bootstrap connection budget and adds transfer timing/throughput logs so we can see whether future bottlenecks are network, reconnects, or transfer behavior.
What Changed
Please make sure these check boxes are checked before submitting
mvn clean test -P default** PR review process **