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 …
-
-
Good question, probably not because of the heavy single-threading assumptions around most of this logic. AFAIK we never implemented code caching for (non-service) workers at all, let alone sharing it between threads.
-
This kind of parallel identical workers use case is an interesting one, not one I've thought about in the past.
- 2 more replies
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.