Running: Gecko/2009/09/06 Firefox 3.5.3
I finally used Sqlite brower to compact it and reduced it to 1,994,752
but it seemed like PlacesCleaner would do even more.
Regards, Jim
Just found a note to myself buried on my desk. The correct extension
should be SqliteManager so I got the wrong one. Sorry.
Regards, Jim
> Last week someone posted about an extension to cleanup and shrink the
> Places.sqlite file. Mine had grown to 4,440,064 so I went looking and
> found PlacesCleaner.
>
> Running: Gecko/2009/09/06 Firefox 3.5.3
>
> I finally used Sqlite brower to compact it
You don't need anything extra, Firefox can do it:
http://blog.mozilla.com/oremj/2009/08/20/speedup-firefox-with-vacuum/
> On 10/11/09 09:10 am, jim byrnes wrote:
>
> > Last week someone posted about an extension to cleanup and shrink the
> > Places.sqlite file. Mine had grown to 4,440,064 so I went looking and
> > found PlacesCleaner.
> You don't need anything extra, Firefox can do it:
> http://blog.mozilla.com/oremj/2009/08/20/speedup-firefox-with-vacuum/
I tried Places Cleaner add-on, Clean Places add-on, and the code snippet
referenced at the link above plugged into the Error Console, and all
changed my places.sqlite from about 15MiB to about . . . 15MiB: Almost
no change using any of them.
--
Regards,
Al S.
>> You don't need anything extra, Firefox can do it:
>> http://blog.mozilla.com/oremj/2009/08/20/speedup-firefox-with-vacuum/
>
> I tried Places Cleaner add-on, Clean Places add-on, and the code snippet
> referenced at the link above plugged into the Error Console, and all
> changed my places.sqlite from about 15MiB to about . . . 15MiB: Almost
> no change using any of them.
It's going to also depend on the amount of history you have configured
to keep. If there's no "empty space" in there from purged history, it's
not going to shrink.
> It's going to also depend on the amount of history you have configured
> to keep. If there's no "empty space" in there from purged history, it's
> not going to shrink.
Exactly. So if there is really a large performance difference when
vacuumin the SQLite file, this reveals more than one performance issue
with the current builds: no automatic vacuuming (when it clearly needs
it), and the declining performance of the SQLite backend when the
database becomes even slightly enlarged.
I mean, really, a 15MiB database is miniscule by today's standards.
--
Regards,
Al S.