The display of the web page and the operation of Mozilla Firefox might become slow while using it a long period because of the expansion of the database though the bookmark and the history, etc. are managed by the database in Firefox.
SQLite Optimizer tries to speed-up Firefox by optimizing these databases.
Optimization : in the initial state is only REINDEX.
When "VACUUM before REINDEX" is selected, it comes to do VACCUM and REINDEX.
- When an extra space of the data base is less than 20%, only REINDEX is done even if it was changed to the setting that does REINDEX after VACUUM.
Meaning of sign when manual operation is executed.
The capital letter on shows vacuum and reindex respectively.
x x cookies.sqlite
% o downloads.sqlite
o o dta_queue.sqlite
x: It failed for the reasons such as locks of the database though it tried to execute.
o :Processing ended normally.
%: (Only the row of V :) Because the fragmentation was 20% or less, it did not execute it though vacuum was specified.
When "After VACUUM, REINDEX is executed" has not been selected, V the under becomes "-".
Whenever ending 10 times, Firefox is optimized when "REINDEX sqlite database on exit" is selected.
When there are a lot of frequencies of the reactivation of a browser and you want to change timing.
Please change the value of sqlite_opt.auto_reindex_per_browser_close from about:config.
· Mozilla Firefox
What's New in This Release: [ read full changelog ]
· Fixed install.rdf.