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

[air/output] Reset heartbeat time in Ray Train after result #37569

Merged
merged 12 commits into from
Jul 20, 2023

Conversation

krfricke
Copy link
Contributor

Why are these changes needed?

Includes #37531.

Currently Ray Train prints a heartbeat every 30 seconds. However, it should only print a heartbeat if it didn't receive a result in the meantime.

With this PR, we reset the heartbeat time when a result arrives. It includes a test to assert the difference between Ray Train and Ray Tune in handling this case.

Related issue number

Closes #36870

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 :(

Kai Fricke added 10 commits July 18, 2023 16:45
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
# Conflicts:
#	python/ray/tune/experimental/output.py
Kai Fricke added 2 commits July 19, 2023 11:51
Signed-off-by: Kai Fricke <kai@anyscale.com>
# Conflicts:
#	python/ray/tune/experimental/output.py
@krfricke krfricke marked this pull request as ready for review July 19, 2023 16:50
@krfricke krfricke requested a review from woshiyyya July 19, 2023 16:50
result: Dict,
**info,
):
self._last_heartbeat_time = time.time()
Copy link
Member

Choose a reason for hiding this comment

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

Why do we reset the heartbeat time here? Is it because we already print a metric table on trial result?

Copy link
Member

@woshiyyya woshiyyya left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you Kai!

@krfricke krfricke merged commit 938c0b0 into ray-project:master Jul 20, 2023
58 of 63 checks passed
@krfricke krfricke deleted the air/output/train-improvements branch July 20, 2023 05:38
NripeshN pushed a commit to NripeshN/ray that referenced this pull request Aug 15, 2023
…ect#37569)

Currently Ray Train prints a heartbeat every 30 seconds. However, it should only print a heartbeat if it didn't receive a result in the meantime.

With this PR, we reset the heartbeat time when a result arrives. It includes a test to assert the difference between Ray Train and Ray Tune in handling this case.

Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: NripeshN <nn2012@hw.ac.uk>
harborn pushed a commit to harborn/ray that referenced this pull request Aug 17, 2023
…ect#37569)

Currently Ray Train prints a heartbeat every 30 seconds. However, it should only print a heartbeat if it didn't receive a result in the meantime.

With this PR, we reset the heartbeat time when a result arrives. It includes a test to assert the difference between Ray Train and Ray Tune in handling this case.

Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: harborn <gangsheng.wu@intel.com>
harborn pushed a commit to harborn/ray that referenced this pull request Aug 17, 2023
…ect#37569)

Currently Ray Train prints a heartbeat every 30 seconds. However, it should only print a heartbeat if it didn't receive a result in the meantime.

With this PR, we reset the heartbeat time when a result arrives. It includes a test to assert the difference between Ray Train and Ray Tune in handling this case.

Signed-off-by: Kai Fricke <kai@anyscale.com>
arvind-chandra pushed a commit to lmco/ray that referenced this pull request Aug 31, 2023
…ect#37569)

Currently Ray Train prints a heartbeat every 30 seconds. However, it should only print a heartbeat if it didn't receive a result in the meantime.

With this PR, we reset the heartbeat time when a result arrives. It includes a test to assert the difference between Ray Train and Ray Tune in handling this case.

Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: e428265 <arvind.chandramouli@lmco.com>
vymao pushed a commit to vymao/ray that referenced this pull request Oct 11, 2023
…ect#37569)

Currently Ray Train prints a heartbeat every 30 seconds. However, it should only print a heartbeat if it didn't receive a result in the meantime.

With this PR, we reset the heartbeat time when a result arrives. It includes a test to assert the difference between Ray Train and Ray Tune in handling this case.

Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Victor <vctr.y.m@example.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[AIR output] Train example: Heartbeat info is not correct when verbose=2
2 participants