You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue or Feature Request Description:
Hi, I'm a former chrome engineer working on a web app now. We've studied some chrome traces of our app where the expiration cache timestamps writes get backed up and cause significant contention. This bottleneck can be alleviated by setting durability: relaxed on any readwrite indexeddb transactions. This prevents blocking on disk flushes. It's the default behavior in Firefox and probably will (or should) be the default in Chrome at some point. That's because it's actually a very significant perf gain for a very minor durability sacrifice -- catastrophic events like power failure, OS crash, disk full may cause data loss, but things like browser crash or tab close do not.
Library Affected:
workbox-expiration
Browser & Platform:
Chrome
Issue or Feature Request Description:
Hi, I'm a former chrome engineer working on a web app now. We've studied some chrome traces of our app where the expiration cache timestamps writes get backed up and cause significant contention. This bottleneck can be alleviated by setting
durability: relaxed
on anyreadwrite
indexeddb transactions. This prevents blocking on disk flushes. It's the default behavior in Firefox and probably will (or should) be the default in Chrome at some point. That's because it's actually a very significant perf gain for a very minor durability sacrifice -- catastrophic events like power failure, OS crash, disk full may cause data loss, but things like browser crash or tab close do not.There's more detail in the chrome status:
https://www.chromestatus.com/feature/5730701489995776
If this behavior makes sense, the fix would entail changing
put
s and similar here:workbox/packages/workbox-expiration/src/models/CacheTimestampsModel.ts
Line 114 in bbaa0bb
Slow (current):
Fast (untested in this context):
The text was updated successfully, but these errors were encountered: