Optimizing for code size by default may hurt performance severely #27
Comments
This was referenced Feb 28, 2019
pastelmind
pushed a commit
to webtoon/psd
that referenced
this issue
Jun 16, 2022
This option is supposed to make the output WASM smaller, but it actually makes the bundle slightly bigger by ~200 bytes. Also, this flag may cause performance issues according to reports (although we personally didn't experience any): rustwasm/wasm-pack-template#27
pastelmind
pushed a commit
to webtoon/psd
that referenced
this issue
Jun 17, 2022
This option is supposed to make the output WASM smaller, but it actually makes the bundle slightly bigger by ~200 bytes. Also, this flag may cause performance issues according to reports (although we personally didn't experience any): rustwasm/wasm-pack-template#27
alexspevak
pushed a commit
to opendesigndev/psd-ts
that referenced
this issue
Jan 16, 2023
This option is supposed to make the output WASM smaller, but it actually makes the bundle slightly bigger by ~200 bytes. Also, this flag may cause performance issues according to reports (although we personally didn't experience any): rustwasm/wasm-pack-template#27
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A topic that recently came up in
#wg-wasmon Discord was that awasm-packproject was performance much more slowly than a raw rustc-generated wasm file. It turned out to be related toopt-level = 's'inCargo.toml, causing a nearly 3x (!) slowdown compared to-C opt-level=3(the default).I'm not sure how often this comes up in the wild though. Unfortunately there's not really a silver bullet here :(. I figured it'd be good to catalog though!
The text was updated successfully, but these errors were encountered: