In Chrome, any JavaScript files in a service worker cache are bytecode-cached automatically.
This means there is 0 parse + compile cost for them on repeat visits.
https://v8.dev/blog/code-caching-for-devs#use-service-worker-caches …
-
-
I mean, I could have read the article
#awkwardThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
AFAIK, it's also limited to JS that's added to the cache during a SW's `install` event (i.e. precaching) and doesn't apply to JS cached during a `fetch` event (i.e. runtime caching).
@wanderview was looking into the tradeoffs of making JS that's runtime cached eligible. -
Correct. Full code cache is install event only atm. I believe
@bashik7 is experimenting with widening that restriction. For other scripts served from cache api the normal code cache will be generated the first time it's loaded by a document.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.