Closed Bug 1510687 Opened 6 years ago Closed 6 years ago

Throttle storage.js update frequency more aggressively

Categories

(WebExtensions :: Storage, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Gijs, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxperf])

Right now we write to disk with a 1500ms deferred task, which is the default for JSONFile.jsm. This is problematic when add-ons spam the storage API in terms of IO volume, as per the last few comments in bug 1419053. IMO we could easily choose to write less frequently (tripping a more immediate write on shutdown if necessary), like once every 30 seconds or whatever. Shane, does that sound reasonable?
Flags: needinfo?(mixedpuppy)
Whiteboard: [fxperf]
This code is all going away in the very near future.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(mixedpuppy)
Resolution: --- → WONTFIX
(In reply to Kris Maglione [:kmag] from comment #1) > This code is all going away in the very near future. Is there a bug open for this?
(In reply to Marco Castelluccio [:marco] from comment #2) > (In reply to Kris Maglione [:kmag] from comment #1) > > This code is all going away in the very near future. > > Is there a bug open for this?
Flags: needinfo?(kmaglione+bmo)
We're moving the back-end of storage.local to indexedDB (see bug 1488825) -- but that ran into a (at least?) DOM-related issue that could cause migration failure which had no ETA, so we ran a study to see how prevalent that might be on a larger audience than Nightly (bug 1502111). The decision on 1488825 should be made within the month.
Flags: needinfo?(kmaglione+bmo)
You need to log in before you can comment on or make changes to this bug.