Explicit memory signals the auto budget folds in alongside navigator.deviceMemory.
cachePoolOverrideBytes is the ?cacheBudgetMB= value (and the native
launcher's equivalent). It MUST reach this budget, not just the caches:
deviceMemory is Chromium-only and spec-capped at 8 GB, so on a large
machine it pins the budget at the 2 GB ceiling and the pool can never be
exercised under pressure at all. The override is the only way to reproduce
constrained-device behaviour on a roomy box.
Explicit memory signals the auto budget folds in alongside
navigator.deviceMemory.cachePoolOverrideBytesis the?cacheBudgetMB=value (and the native launcher's equivalent). It MUST reach this budget, not just the caches:deviceMemoryis Chromium-only and spec-capped at 8 GB, so on a large machine it pins the budget at the 2 GB ceiling and the pool can never be exercised under pressure at all. The override is the only way to reproduce constrained-device behaviour on a roomy box.