Thanks for sending the intent and for experimenting with the MemoryCache! On Fri, Mar 17, 2023 at 7:08 PM 'Jiacheng Guo' via blink-dev < blink-dev@chromium.org> wrote:
> Contact emails...@google.com > > Explainer > https://docs.google.com/document/d/1jcdXkoFBbdxmp_EYIrrOJvEgYd0hGBAr4Nbno7KWnIs/edit?usp=sharing > > SpecificationThe feature is not web-spec related. > The situation as I remember it is a bit more complex than that :) I think the memory cache is defined for images <https://html.spec.whatwg.org/multipage/#the-list-of-available-images>, but not for other resource types. So if we end up changing the behavior for images, it'd be good to see if we can reflect that behavior change in the spec. And ideally, it'd be great if we're able to actually specify the behavior of the memory cache once we figure out where we want it to land, as I believe it is observable. (Through ResourceTiming, as well as timing in general). > > Design docs > > https://docs.google.com/document/d/1jcdXkoFBbdxmp_EYIrrOJvEgYd0hGBAr4Nbno7KWnIs/edit?usp=sharing > > Summary > > To measure the impact of garbage collection on Blink memory cache and > potential performance boost, we plan to keep strong references to loaded > resources in the Blink memory cache. The change will serve as an estimation > only project to collect data about the maximal cache hit rate with all > resources available. > > > Blink componentBlink>Loader > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELoader> > > TAG review > TAG review is not required since the experiment changes the internal > behavior of renderer and is transparent to the websites and web developers. > > Risks > > > Interoperability and Compatibility > > > Resource reference lifetime does not affect the behavior of the browser. > We do not expect there to be interoperability or compatibility issues. > > *Gecko*: No signal > > *WebKit*: No signal > > *Web developers*: No signals > > *Other signals*: > > WebView application risks > > The change does not modify the behavior of web APIs > > Goals for experimentation > > The four configurations will be launched on dev/canary. The combinations > are: * The control group. No strong reference to resources. * Save strong > references for all resources of all types for all the pages. * Save strong > references for only script, fonts and stylesheets for all pages. * Save > strong references for all resources for only one page. * Save strong > references for only script, fonts and stylesheets for only one page. > Can you explain the differences between the "for all the pages" and the "only one page" variants? > We will evaluate the following metrics under different configurations * > Core web browsing metric (FCP/LCP etc) * Cache hit rate: > Blink.MemoryCache.RevalidationPolicy > Could we also count how many resources are no longer loaded over the network? (so are now a MemoryCache HIT that were formerly an HTTP cache MISS) > * Memory footprint * Crash Rate > > > Reason this experiment is being extended > > > > Ongoing technical constraints > > > > Debuggability > > > > 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 > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?No, resource reference lifetime in blink is invisible to the websites. > > Flag nameMemoryCacheStrongReference for the overall configuration. > MemoryCacheStrongReferenceSingleUnload and > MemoryCacheStrongReferenceFilterImages for sub configurations > > Requires code in //chrome?False > > Tracking bughttps://crbug.com/1409349 > > Estimated milestones > > The feature is for experiment only. We do not expect to launch it to > stable as it is. If the experiment provides positive results, we will move > on to further refine the resource lifetime management strategy in Blink. > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5196823129489408 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > 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+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJQw1NwNzokqhvwtnrV-J-8BeMeRjfC-cvkXMBmZYK4Vej%3DX%2Bg%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJQw1NwNzokqhvwtnrV-J-8BeMeRjfC-cvkXMBmZYK4Vej%3DX%2Bg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVa3MedVWNLasEn4bK0aORyXBDnL1stw8Nu%2BFZvrBjBPg%40mail.gmail.com.
