You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although the .whl files are cached between code runs, the fact that we need to reset pyodide between runs means that they need to be re-interpreted each time the code runs. This introduces some latency which we may be able to reduce if we cache using WebAssembly modules (see Slack thread for more details)
The text was updated successfully, but these errors were encountered:
There is a noticeable delay of around 5 seconds at the start of each code run using sklearn as a (rather large) example, but this is just over a second for something like numpy (which perhaps we are more likely to use)
It may be possible to cache the wasm files, but this thread suggests it's complicated and may not make enough to difference to be worth it
loiswells97
changed the title
Cache WebAssembly modules to reduce latency
Spike: Investigate caching WebAssembly modules to reduce latency
Mar 18, 2024
Although the
.whl
files are cached between code runs, the fact that we need to resetpyodide
between runs means that they need to be re-interpreted each time the code runs. This introduces some latency which we may be able to reduce if we cache using WebAssembly modules (see Slack thread for more details)The text was updated successfully, but these errors were encountered: