Open
Bug 1474521
Opened 6 years ago
Updated 2 years ago
Forcibly run idle maintenance if we were unable to run it for a while
Categories
(Toolkit :: Places, enhancement, P3)
Toolkit
Places
Tracking
()
NEW
People
(Reporter: mak, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxsearch])
We noticed cases where idle maintenance doesn't run for some users, possibly due to the way they use the browser (short active sessions), or idle measuring bugs.
In those cases we should force an idle maintenance, maybe once a month or once every 2 months.
We should probably check the current queries to find possibly slow ones (for some users idle maintenance seems to take 10 seconds or such).
Reporter | ||
Comment 1•6 years ago
|
||
Since one of the long poles of maintenance is integrity_check, when we forcibly run maintenance we could instead use quick_check to avoid interrupting the user for too long.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•