Switch to auto-vacuum
Categories
(Application Services :: Remote Settings, enhancement)
Tracking
(Not tracked)
People
(Reporter: bdk, Assigned: bdk)
References
Details
(Whiteboard: [fxsync-])
We're triggering alerts on iOS because of large writes in the remote settings component. This seems to come from us executing VACCUM, which causes the entire database file to be written to disk. I believe they're seeing writes of 500MB or so in practice, which is pretty high for a daily operation on mobile. That size could be wrong, I haven't spent much time investigating. However, the DB size will grow no matter what.
We should replace the full vaccums with auto-vacuum. auto-vaccum will reclaim free space without requiring a writing out the entire DB file. It doesn't defragment the database which could be worse for performance, but I don't expect this to be an issue. If it is, we can revisit and do a full vaccum every once in a while.
|
||
Updated•22 days ago
|
|
Assignee | |
Comment 1•6 days ago
|
||
Looking into this more, I realized that remote settings already does this because it uses the sql_support::run_maintenance.
The one caveat is that https://bugzilla.mozilla.org/show_bug.cgi?id=2064759 might be causing us to do a full vacuum the first time to enable incremental vacuuming. I'm going to close this one and work on that one instead.
Description
•