-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
krfricke
merged 12 commits into
ray-project:master
from
krfricke:air/output/train-improvements
Jul 20, 2023
Merged
[air/output] Reset heartbeat time in Ray Train after result #37569
krfricke
merged 12 commits into
ray-project:master
from
krfricke:air/output/train-improvements
Jul 20, 2023
Conversation
This file contains 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
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
8 tasks
# Conflicts: # python/ray/tune/experimental/output.py
woshiyyya
reviewed
Jul 20, 2023
result: Dict, | ||
**info, | ||
): | ||
self._last_heartbeat_time = time.time() |
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.
Why do we reset the heartbeat time here? Is it because we already print a metric table on trial result?
woshiyyya
approved these changes
Jul 20, 2023
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. Thank you Kai!
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
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.
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
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.