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 …
-
Show this thread
-
Replying to @mathias
In the very unlikely event of fetching a JS file to parse as a string would it have to fetch it again?
2 replies 0 retweets 0 likes -
Replying to @Lady_Ada_King @mathias
Both the source and bytecode are cached, and the latter is invalidated more frequently, eg if you update Chrome & V8 changes
3 replies 0 retweets 2 likes
Replying to @jaffathecake @Lady_Ada_King
Important nuance: the eval cache exists in-memory only. The generic bytecode cache lives on disk for hot runs. So we would actually re-parse + re-compile source text strings that are evicted from memory.
5:07 AM - 9 Apr 2019
0 replies
0 retweets
2 likes
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.