-
Notifications
You must be signed in to change notification settings - Fork 16
factor out weight cleanup to separate file, also non-blocking now #292
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
casteryh
wants to merge
12
commits into
main
Choose a base branch
from
weight-cleanup-fix
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.
Open
Changes from 6 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
7643064
add back drop_weights, factoring it out
casteryh e66efee
import time
casteryh c8b2b42
refactor
casteryh 73d233c
Merge branch 'main' into weight-cleanup-fix
casteryh cee8d29
only keep one version
casteryh 0b5edb7
move dcp_handle drop to separate thread
casteryh 19e5100
Move torchstore_utils from actors to utils
Jack-Khuu cf5dab5
Merge branch 'main' into move-ts-util
Jack-Khuu 5fe537f
Merge branch 'main' into weight-cleanup-fix
casteryh e91f66c
Merge branch 'move-ts-util' into weight-cleanup-fix
casteryh d517a9a
fix test
casteryh 90a2dba
clean up
casteryh 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
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.
How are you confirming this all finishes before adding more weights?
Also in typical async form this step would just be an async method that you'd await now or later. Why is there an extra method called "wait"?
Uh oh!
There was an error while loading. Please reload this page.
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.
I thought the point is you don't, if you just need the weight to be eventually deleted. when you do
step()
, the task is scheduled in the background and everything else proceeds as normal.Yes but in that case, if we want to schedule the task in the background and not await for it, we need to manage the task in
main.py
, which we supposedly don't want to do. This essentially hides the task scheduling logic in the WeightCleaner class.If you want to make sure all the scheduled tasks are indeed completed (i.e. all old weights are deleted. like you mentioned earliner), you can
await weight_cleaner.wait()
. Presumably this can be named better, let me know what you think.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.
My understanding is, in typical async code, if you don't explicitly create a task, then it will never get executed unless you await on it? I think we can also always schedule the task and return a join handle.