166481 2016-12-26 09:39:44 -0800 WebAssembly: implement the IndexDB caching API 2020-03-25 16:16:58 -0700 1 1 1 Unclassified WebKit JavaScriptCore WebKit Nightly Build Unspecified Unspecified RESOLVED CONFIGURATION CHANGED P2 Normal --- 168264 161709 166480 1 jfbastien webkit-unassigned ashvayka chi187 dpaddock gauravdewan007 jfbastien keith_miller saam oldest_to_newest 1262750 0 jfbastien 2016-12-26 09:39:44 -0800 As described here: https://github.com/WebAssembly/design/blob/master/JS.md#structured-clone-of-a-webassemblymodule > Structured Clone of a WebAssembly.Module > > A WebAssembly.Module is a cloneable object† which means it can be cloned between windows/workers and also stored/retrieved into/from an IDBObjectStore‡. The semantics of a structured clone is as-if the binary source, from which the WebAssembly.Module was compiled, were cloned and recompiled into the target realm. Engines should attempt to share/reuse internal compiled code when performing a structured clone although, in corner cases like CPU upgrade or browser update, this may not be possible and full recompilation may be necessary. > > Given the above engine optimizations, structured cloning provides developers explicit control over both compiled-code caching and cross-window/worker code sharing. ─ † https://html.spec.whatwg.org/multipage/infrastructure.html#cloneable-objects ‡ https://w3c.github.io/IndexedDB/#object-store 1359118 1 gauravdewan007 2017-10-11 04:22:08 -0700 This can give a great push to startup time as mentioned in https://bugs.webkit.org/show_bug.cgi?id=178163 For example startup time of webassembly app which takes 2+ sec on Safari 11 on a latest fast mac machine gets loaded from indexeddb in less than 200 milliseconds. 1359205 2 jfbastien 2017-10-11 09:02:11 -0700 *** Bug 178163 has been marked as a duplicate of this bug. *** 1507772 3 chi187 2019-02-19 12:25:23 -0800 This could be closed per https://github.com/WebAssembly/spec/issues/821 IndexedDB should be replaced by Caching API