-
Notifications
You must be signed in to change notification settings - Fork 174
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
Improve WASM loading performance #2654
Labels
Milestone
Comments
AlexeyGirin
added
the
Test Cases Written
Test cases has been written for that issue
label
May 7, 2024
No test cases needed for that particular issue |
rrodionov91
added a commit
that referenced
this issue
Jun 25, 2024
- added two ketcher-standalone builds: with base64 indigo wasm and with separate wasm file
rrodionov91
added a commit
that referenced
this issue
Jun 25, 2024
- added two ketcher-standalone builds: with base64 indigo wasm and with separate wasm file
9 tasks
rrodionov91
added a commit
that referenced
this issue
Jun 26, 2024
- added two ketcher-standalone builds: with base64 indigo wasm and with separate wasm file - updated indigo to 2.22.0-rc.2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Background
At the moment, WASM is embed as base64 string into JS-file. This needs to be changed to speed up WASM load.
Solution
Extract
.wasm
part from JS to separate file. This would reduce the file size and allow browser to cache WASM and speed up future loads.Related Indigo issue: epam/Indigo#877
#185972429
Need to check integration with backend after indigo ticket will be completed.
The text was updated successfully, but these errors were encountered: