You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the conversation on WebNN and WebGPU interop session, at the WebGPU F2F meeting in San Francisco, Myles Maxfield made an observation about the fact that WebNN MLContext is a single-device context. He raised the awareness that Apple's CoreML can distribute a workload within a single ML graph across multiple devices including the ANE, and said that it would be nice if WebNN has a provision to support that situation as well.
I think this feedback is related to a discussion in the working group of late about ways to create a notion of a default MLContext (when there is no explicit device associated with the context -- either a CPU device or a WebGPU device) that is more open to the implementation. This default context could effectively be whatever the implementer wants it to be including a multi-device context in the case of the Apple's WebKit implementation over CoreML.
The text was updated successfully, but these errors were encountered:
During the conversation on WebNN and WebGPU interop session, at the WebGPU F2F meeting in San Francisco, Myles Maxfield made an observation about the fact that WebNN
MLContext
is a single-device context. He raised the awareness that Apple's CoreML can distribute a workload within a single ML graph across multiple devices including the ANE, and said that it would be nice if WebNN has a provision to support that situation as well.I think this feedback is related to a discussion in the working group of late about ways to create a notion of a default MLContext (when there is no explicit device associated with the context -- either a CPU device or a WebGPU device) that is more open to the implementation. This default context could effectively be whatever the implementer wants it to be including a multi-device context in the case of the Apple's WebKit implementation over CoreML.
The text was updated successfully, but these errors were encountered: