Intent to Experiment: CacheStorage Code Cache Hint

[Ben Kelly]

Contact emails wande...@chromium.org Explainer

See the public design doc. Design docs/spec

https://docs.google.com/document/d/1egza-w5KA7-03T5zZtQTwBNWAg2zHxFFoOS2UgMdAh8/edit#   TAG review

None yet. I would like to collect data with our partner before we decide whether it's worth taking on the work to standardize this kind of hinting mechanism. Summary This experiment will allow participating sites to provide hints to cache_storage that full code cache should not be generated in a service worker install event. The hint will be communicated as a header on the Response being stored. This is a change to an unspecified optimization in chrome. Full code cache generation during the install event was added in M64. It is only observable indirectly through changes in timing and disk quota usage. Goals for experimentation There are clear trade-offs to generating full code cache.  Partners have told us it clearly improves load times.  The binaries are quite larger, however, and also lead to increased disk and runtime memory usage.

We have a partner interested in providing hints so that they can gain the loading benefits for critical scripts and avoid the binary bloat for non-critical scripts.

If the data shows a benefit we will investigate standardizing a hinting mechanism.

Experimental timeline M80 to M82 Ongoing technical constraints None. Debuggability There are no plans for additional devtools support in this trial. It is possible to see when code cache is used via the performance timeline tab. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes Is this feature fully tested by web-platform-tests? No. Code caching is currently considered a browser optimization and not addressed by any spec. Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5685099288854528  

[Yoav Weiss]

Interesting case of running an origin trial before design & implementation!

Validation here before investing in the feature makes perfect sense.

LGTM

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK7rkMiPhapMSHQ9NNoHRkhTTzNJrzPF6UiPJddOmwgUpjxKqg%40mail.gmail.com.

[Ben Kelly]

FYI, my partner was unable to participate in this trial due to competing priorities.  I plan to let this trial expire and pick it up again when they have time later this year.  Also note, the expiration will be at the end of M81 since M82 was removed from the release schedule.

[Ben Kelly]

Hello Blink API Owners.  I'd like to restart this origin trial now that I have partners ready to test with it.  AIUI I don't need to wait for a new release, so it would start in the tail end of M83 through M86.

[Yoav Weiss]

Still LGTM! :)