Refactor gpu-remoting workload sender scripts - #54
Merged
yumemiso merged 1 commit intoJul 29, 2026
Merged
Conversation
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
This PR refactors duplicated workload sender logic in
gpu-remotingby extracting the shared command-building and trace-replay flow into a common module.Changes
workload_sender.pymoduleclient_sender.pyinto a thin entrypoint for the default gpu-remoting environmentscheduler/cluster_client_sender.pyinto a thin entrypoint for the scheduler/cluster environmentWhy
Both sender scripts previously duplicated nearly the same implementation, which made them harder to maintain and easy to drift apart. This change keeps existing behavior while reducing duplication and making future sender-side updates easier.
Validation
python3 -m py_compile