-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[RLlib] Old API stack IMPALA/APPO: Re-introduce mixin-replay-buffer pass, even if replay-ratio=0
(fixes a memory leak).
#49964
[RLlib] Old API stack IMPALA/APPO: Re-introduce mixin-replay-buffer pass, even if replay-ratio=0
(fixes a memory leak).
#49964
Conversation
Signed-off-by: sven1977 <[email protected]>
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.
LGTM. Just a short question to the "mixin" buffer.
replay_ratio=self.config.replay_ratio, | ||
replay_mode=ReplayMode.LOCKSTEP, | ||
) | ||
self.local_mixin_buffer = MixInMultiAgentReplayBuffer( |
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.
Dumb question: why do we even have a "mixin" replay buffer. Couldn't we just use a normal one and mix the batch in by ratio?
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.
see my answer below
replay_ratio=self.config.replay_ratio, | ||
replay_mode=ReplayMode.LOCKSTEP, | ||
) | ||
self.local_mixin_buffer = MixInMultiAgentReplayBuffer( |
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.
Dumb question: why do we even have a "mixin" replay buffer. Couldn't we just use a normal one and mix the batch in by ratio?
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.
We could, but then again: This is old API stack. Not the time for any changes or experiments ;)
…ass, even if `replay-ratio=0` (fixes a memory leak). (ray-project#49964) Signed-off-by: Anson Qian <[email protected]>
…ass, even if `replay-ratio=0` (fixes a memory leak). (#49964)
…buffer pass, even if `replay-ratio=0` (fixes a memory leak). (ray-project#49964)" This reverts commit 84b2b0e.
…buffer pass, even if `replay-ratio=0` (fixes a memory leak). (ray-project#49964)" This reverts commit 84b2b0e.
Signed-off-by: Jiajun Yao <[email protected]>
…ass, even if `replay-ratio=0` (fixes a memory leak). (ray-project#49964) Signed-off-by: Puyuan Yao <[email protected]>
Signed-off-by: Jiajun Yao <[email protected]>
Old API stack IMPALA/APPO: Re-introduce mixin-replay-buffer pass, even if
replay-ratio=0
(fixes a memory leak).Why are these changes needed?
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.