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.


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.


Status in Chromium


Origin trial (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signals


Last updated on 2021-12-13