Skip to content
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.

Sign up for GitHub

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

Jump to bottom

DOC Optimizing WASM browser compilation time #15249

Open
rth opened this issue Oct 6, 2021 · 0 comments
Open

DOC Optimizing WASM browser compilation time #15249

rth opened this issue Oct 6, 2021 · 0 comments
Labels
docs good first bug help wanted

Comments

@rth
Copy link
Contributor

rth commented Oct 6, 2021 •
edited
Loading

The documentation on optimizing compilation and optimizing load time are quite nice.

I wonder if anyone could share optimization advice specifically for the WASM compilation time in the browser. Are there options that are known to affect it, well besides the size of the produced .wasm objects? We found out that it's the bottleneck in Pyodide for large scientific Python packages (pyodide/pyodide#347 (comment))

Also the documentation on the manual persistance of compiled modules to IndexedDB might need to be updated,
https://github.com/emscripten-core/emscripten/blame/2595d3f703b6d6eaf312a2b027ef66c6ab3c1031/site/source/docs/compiling/Deploying-Pages.rst#L44
since that was deprecated WebAssembly/spec#821
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
docs good first bug help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kripken @rth