-
Notifications
You must be signed in to change notification settings - Fork 692
Remote reconnection improvement #3305
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3305 +/- ##
==========================================
+ Coverage 82.66% 82.69% +0.03%
==========================================
Files 995 995
Lines 127626 127822 +196
==========================================
+ Hits 105498 105708 +210
+ Misses 22128 22114 -14 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Regarding your drop_client
issues.. should we also have a Drop
implementation to clean up the tasks when dropped?
pub fn register_empty_tensor(&self, id: TensorId, shape: Vec<usize>, dtype: DType) -> TensorIr { | ||
let mut ctx = self.context.lock().unwrap(); | ||
|
||
let shape = Shape { dims: shape }; |
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.
You can just call shape.into()
(Shape
implements From<Vec<usize>>
)
Drop is implemented for WsSender, which is dropped when the last WsClient is dropped. This is what triggers the "close" flag for the workers. There are no issues now with drop_client. |
Just tested the mnist example using the remote backend and there seems to be an issue with the handle container, which then causes the lock to be poisoned.
It looks like the tensor handle issue still exists. Just tried running one of the examples (mnist) with the remote backend:
|
This PR has been marked as stale because it has not been updated for over a month |
This PR has been marked as stale because it has not been updated for over a month |
burn-remote
Added reconnection attemts when the Websocket streams fail. At every reconnection, a new session ID is created.
(Bug fix): Added a
RegisterEmptyTensor
compute taskRefactored client worker
Improved tests
burn-router
drop_client()
I had an issue where my tests would hang, because the websocket client had started threads. Adding
drop_device
allows me to explicitly close the websocket client in my tests.