Change to storage pressure handling -- need launch review?

[Evan Stade]

Hi blink-dev,

On the storage team we are considering modifying the process by which Chromium attempts to resolve storage pressure. The rather hand-wavey spec is here[1]. Our changes will not affect any existing IDL or change conformance to any spec we know of. Our changes may be one or more of the following:

• adjusting the definition of "storage pressure", i.e. what triggers a round of eviction
• adding a hard expiration date for old best-effort buckets
• modifying which buckets are deleted under pressure situations (e.g. evicting extra data or larger chunks of data, instead of the bare minimum amount of LRU data as Chromium currently does)

My impression from reading this document [2] is that this is not a web-facing change and thus does not require any launch review, but we wanted to reach out to you to confirm or deny this point. Please advise!

[1] https://storage.spec.whatwg.org/#storage-pressure

[2] ]https://www.chromium.org/blink/launching-features/

-- Evan Stade

[Yoav Weiss]

This indeed doesn't sound like a web-exposed change. It could potentially be observable in theory (e.g. by developers deliberately creating storage pressure and seeing eviction happening at different points in time than before), but it seems unlikely that this is something developers grew to rely on in meaningful ways in practice.

So, I tend to agree that this doesn't require an intent.

--
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/CAO4XGS-d0NuFM%2BU_EdLJVODPTVV14ybX5zJ%3DKqx6K9Cg_9BCRQ%40mail.gmail.com.