Firefox/Projects/Places Vacuum: Difference between revisions

(Created page with '= Overview = '''Sprint lead:''' mak '''Sprinters:''' '''Description''' :Fragmented Sqlite databases are known to make awesomebar performances bad, and cause other perf pr…')
 
Line 45: Line 45:


== Currently investigated options ==
== Currently investigated options ==
** '''Vacuum with a button''': discarded, we don't want users to have to rememeber they should vacuum.
* '''Vacuum with a button''': discarded, we don't want users to have to rememeber they should vacuum.
** '''Vacuum in background''': Possible for small databases, but for databases like places.sqlite that can take one hundred megabytes, is just not feasible
* '''Vacuum in background''': Possible for small databases, but for databases like places.sqlite that can take one hundred megabytes, is just not feasible
** '''Vacuum on major upgrade''': This would be a good compromise, but has some drawback. First of all there is a feeling that making upgrades slower will cause users to delay them. Secondly it would be a Firefox only fix. Third it would put someting storage related in update code.
* '''Vacuum on major upgrade''': This would be a good compromise, but has some drawback. First of all there is a feeling that making upgrades slower will cause users to delay them. Secondly it would be a Firefox only fix. Third it would put someting storage related in update code.
** '''Vacuum on idle''': This is the currently taken in count solution.
* '''Vacuum on idle''': This is the currently taken in count solution.
** '''Better vacuum support in SQLite''': this is the long term solution
* '''Better vacuum support in SQLite''': this is the long term solution


=== Vacuum on idle ===
=== Vacuum on idle ===
Confirmed users
595

edits