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 …
-
-
Yes, good point, it wasn't available last I check but I last checked a while ago. Let's check again, seems that this is now the same info as tracing provides.
-
I would vote that this information should be exposed by default in devtools w/o having to flip feature flags on.
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.