Is burn-train
+ metrics
+ wasm
a goal?
#2875
AlexErrant
started this conversation in
Ideas
Replies: 1 comment
-
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I believe that
burn-train
+wasm
is a goal. Should themetrics
feature work on wasm?I'm maintaining a small fork of burn(-train) that runs on browser-wasm (ref) that uses functionality gated by
metrics
. In the process of upgrading to v0.16.0, I ran into two areas of interest. Note that both are related to wasm and not browser-wasm.async_channel
callsrecv_blocking
here, which is not supported on wasm. The dependency onasync-channel
was added with the PR "Consistent sync/async handling, allow more functions to be async for wasm". There may be a future where it is supported, but there's currently no momentum. I deleted AsyncProcessor in my fork.metrics
usesnvml-wrapper
which doesn't work with wasm. Ifburn-train
+metrics
+wasm
is a goal, should we gatenvml-wrapper
behind ametrics-cuda
flag?Beta Was this translation helpful? Give feedback.
All reactions