We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a tracking issue for issues running axon simulations under GPU on web browsers.
Firefox nightly has webgpu support, and it is built on top of the rust wgpu that we successfully use in native mode: https://github.com/gfx-rs/wgpu
Unfortunately, it has a severe performance bug in mapAsync that makes it unusuable:
gpu/examples/compute has timing that demonstrates the bug.
gpu/examples/compute
Chrome has production webgpu enabled, but it enforces an (unnecessary) limit of 10 buffers per stage, while axon requires 24.
Otherwise, on the compute example it is just as fast as wgpu native.
Production safari can enable webgpu in developer settings / feature flags, but it doesn't even work for basic graphics.
Technology preview does better, mostly working with the 2D Draw graphics, but the 3D netview is glitchy
The gpu/examples/compute runs, is 2x slower overall but the mapAsync part is reasonably fast / comparable to native.
run axon/examples/ra25 using core run web
core run web
No response
macOS
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
This is a tracking issue for issues running axon simulations under GPU on web browsers.
Firefox
Firefox nightly has webgpu support, and it is built on top of the rust wgpu that we successfully use in native mode: https://github.com/gfx-rs/wgpu
Unfortunately, it has a severe performance bug in mapAsync that makes it unusuable:
gpu/examples/compute
has timing that demonstrates the bug.Chrome
Chrome has production webgpu enabled, but it enforces an (unnecessary) limit of 10 buffers per stage, while axon requires 24.
Otherwise, on the compute example it is just as fast as wgpu native.
Safari
Production safari can enable webgpu in developer settings / feature flags, but it doesn't even work for basic graphics.
Technology preview does better, mostly working with the 2D Draw graphics, but the 3D netview is glitchy
The
gpu/examples/compute
runs, is 2x slower overall but the mapAsync part is reasonably fast / comparable to native.How to reproduce
run axon/examples/ra25 using
core run web
Example code
No response
Relevant output
No response
Platform
macOS
The text was updated successfully, but these errors were encountered: