Closed
Bug 1166814
Opened 10 years ago
Closed 7 years ago
Automatically prune visits and history items
Categories
(Firefox for iOS :: Data Storage, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1131737
Tracking | Status | |
---|---|---|
fxios | + | --- |
People
(Reporter: rnewman, Unassigned, Mentored)
References
Details
(Keywords: perf, Whiteboard: dupeme)
Attachments
(1 file)
64.50 KB,
text/plain
|
Details |
We should clear these, both deleted and not deleted, oldest first, preferring those that have already been synced, as our database swells.
Reporter | ||
Updated•10 years ago
|
Whiteboard: dupeme
Reporter | ||
Comment 1•10 years ago
|
||
My browser DB from my 6S is 10MB:
sqlite> select count(*) from favicons;
852
sqlite> select count(*) from visits;
36223
sqlite> select count(*) from domains;
1879
sqlite> select count(*) from tabs;
49
sqlite> select count(*) from favicon_sites;
2540
sqlite> select count(*) from history;
18185
Reporter | ||
Comment 2•10 years ago
|
||
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Comment 3•8 years ago
|
||
Note that we _never_ clean up deleted history items for non-Sync users, as far as I can tell; they sit around with is_deleted=1 and a blanked URL, slowing down queries and occupying disk space.
This bug is a two-parter:
1. DELETE existing items with is_deleted. All of them if we aren't Sync users, and old ones if we are.
2. Prune old items when we start running out of space or start slowing down.
Blocks: 1317543
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•