-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Fix forced lag initial conditions #4056
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tdene
wants to merge
6
commits into
NVIDIA:main
Choose a base branch
from
tdene:tde/fix_forced_lag
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+61
−14
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't this change the semantics of enforce_order? So, now enforce_order preserves the staleness order, not the submission order?
Regardless of the answer, we need to have a docstring for GroupedRolloutRequest to describe what this actually means, right now it is unclear.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done! I believe my docstring also reflects the discussion below; let me know if not.
It changes the semantics of
enforce_order, so thatenforce_orderis completely ignored during warm-up (the firstnum_workersbatches).The goal of
enforce_orderis to guarantee that each training batch is composed of rollouts of a specific, pre-determined, staleness. During "warmup", all rollouts consumed by training were started on iteration 0; this is just how warmup needs to work. Because all rollouts have equal staleness, it makes no sense to preserve their submission order; we get no benefit out of it, only drawbacks.So this is an optimization at warmup, to make it smoother. And because forced lag really struggles to smooth out its per-step behavior after warmup (unlike the smooth behavior you are used to seeing from unforced lag, where it's only the first few steps that are bumpy, with forced lag the bumpyness of the first few steps causes the entire run to show a saw-tooth pattern on throughput numbers), this optimization makes the entire run slightly smoother.
It is just a free win. The only drawback is that other RL projects that exist in the open-source community are not taking this free win, so our forced lag simulations will be a steel-man of how forced lag is actually implemented by others.