Caching of compiled modules into IndexedDB was deprecated [1] [2]. There is a blog post on the v8 blog about caching [3] posted after the IndexedDB caching was deprecated. Is the information in the post still up to date? I am asking because I can't replicate the tracing with chrome://tracing
; I am not seeing the caching-related function calls in the tracing.
Otherwise, is there some caching of compiled modules in firefox or other browsers?
[1] https://github.com/WebAssembly/spec/issues/821
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1469395
[3] https://v8.dev/blog/wasm-code-caching
Did you use compileStreaming or instantiateStreaming?
I tried both (the live demos from [1] and [2])
I also see compileStreaming and instantiateStreaming in the trace:
image.png
[1] https://developer.mozilla.org/en-US/docs/WebAssembly/JavaScript_interface/compileStreaming#compile_streaming
[2] https://developer.mozilla.org/en-US/docs/WebAssembly/JavaScript_interface/instantiateStreaming#instantiating_streaming
Last updated: Dec 23 2024 at 12:05 UTC