-
Notifications
You must be signed in to change notification settings - Fork 926
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
Reduce the binary size #1464
Comments
This is espcially important on wasm/webgl, where the blob has to be shipped over the wire. Currently our examples, built in release, sit at about 5-6MB uncompressed. |
I can confirm this for WebGL builds. Not for builds which use WebGPU. I'm currently at 1.6Mb uncompressed (Gziped its 571k.). The reason for this could also be that Steps I've completed so far:
Further ideas: https://rustwasm.github.io/book/reference/code-size.html I think that the uncompressed size should be below 1Mb, else the compilation on the client side could be a real bottleneck (CPU fans spin up etc.). In comparison for WebGPU my build size is already 708k without compression (compressed its down to 222k). |
@kvark did you use the WebGL backend or WebGPU? |
I didn't measure either, just linked to a tweet. |
I might do some better reproducible measurements soon :) Something that would be awesome would be a CI step which validates that WASM builds are not exploding in size. If the size of the wasm file doubles for example with the introduction of a commit then there is a serious problem. |
This has no particular actionability, so I'm going to close. |
See https://twitter.com/batmansmk/status/1346479574465433613
A simple app got compiled to an 1.3Mb executable. I'm sure we can do better!
The text was updated successfully, but these errors were encountered: