Skip to content
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] MetricsLogger cleanup throughput logic. #49981

Merged

Conversation

sven1977
Copy link
Contributor

@sven1977 sven1977 commented Jan 21, 2025

MetricsLogger cleanup throughput logic.

  • For simplicity, MetricsLogger/Stats should automatically compute the throughput for all keys that have reduce=sum and clear_on_reduce=False ("lifetime counts").
  • There is no performance hit to do so.

Why are these changes needed?

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Signed-off-by: sven1977 <svenmika1977@gmail.com>
Signed-off-by: sven1977 <svenmika1977@gmail.com>
@sven1977 sven1977 added rllib RLlib related issues rllib-logging This problem is related to logging metrics rllib-newstack labels Jan 21, 2025
Copy link
Collaborator

@simonsays1980 simonsays1980 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Just a small question.

self._throughput = 0.0
self._measure_throughput = False
if (
self._reduce_method == "sum"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dumb question: Why is this only relevant for sum? Because these are the only lifetime stats?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only reduce setting, for which it makes sense to measure throughput for. Doesn't really make sense for min/max/mean.

Signed-off-by: sven1977 <svenmika1977@gmail.com>
Signed-off-by: sven1977 <svenmika1977@gmail.com>
@sven1977 sven1977 enabled auto-merge (squash) January 22, 2025 09:28
@github-actions github-actions bot added the go add ONLY when ready to merge, run all tests label Jan 22, 2025
@sven1977 sven1977 merged commit 68527f2 into ray-project:master Jan 22, 2025
6 of 7 checks passed
@sven1977 sven1977 deleted the metrics_logger_cleanup_throughput branch January 22, 2025 12:29
win5923 pushed a commit to win5923/ray that referenced this pull request Jan 23, 2025
simonsays1980 pushed a commit to simonsays1980/ray that referenced this pull request Jan 23, 2025
anson627 pushed a commit to anson627/ray that referenced this pull request Jan 31, 2025
Signed-off-by: Anson Qian <anson627@gmail.com>
anson627 pushed a commit to anson627/ray that referenced this pull request Jan 31, 2025
Signed-off-by: Anson Qian <anson627@gmail.com>
anyadontfly pushed a commit to anyadontfly/ray that referenced this pull request Feb 13, 2025
Signed-off-by: Puyuan Yao <williamyao034@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests rllib RLlib related issues rllib-logging This problem is related to logging metrics rllib-newstack
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants