大家的的places.sqlite有多大

我的FF，用了半年，经过手工清理，现在的places.sqlite大小大概为1M。。。

在管理书签里面把上月鸡以前的历史都删除了，还有2.5M大 不删除有9M大

两年，11.9M

placescleaner发布帖子在这
檢視主題 - PlacesCleaner 收藏庫清潔工 • Mozilla Taiwan 討論區

用了placescleaner之后还有有20M ，可见placescleaner删除访问次数少于N次的记录，效果并不明显，因为历史记录很多都是重复的。。。。若是按照日期来删除，保留一个月以来的数据，至少可以删除到1M左右。placescleaner的开发者不知道来不来这个论坛，要是他能添加一个按照时间来删除的功能，那俺就不用再费事了，最近忙着找工作，没空写扩展哟，呵呵。。。

看了看有三个月之前的历史纪录,应该和shenyixin99说的一样,有4万条历史纪录,1000个书签，别是以前瞎折腾弄坏了，准备备份书签后让firefox重建
=======================================
压缩了之后有24M
=======================================
用了placescleaner之后有20M
=======================================
删除后重建有684k，连小图标都没了，tag之类的完整保留
=======================================
还是用最少保存30天的设置，如果不再折腾并且还记得有这么码事的话，半年后挖坟

30天能上26M，你书签比历史都多吧

我的是26M，保存30天的，刚开始的时候折腾过一次，后来就不管了，应该是稳定在这个大小了，要是定期整理怪麻烦的

252KB

我的只有344K,安装好第一次运行我就设置历史记录为1天.

Vacuuming and zero-fill

Sqlite has a VACUUM command to compress unused space from the database. Sqlite works like a memory manager or a file system. When data is deleted, the associated bytes are marked as free but are not removed from the file. This means that the file will not shrink, and some data may still be visible in the file. The way to work around this is to run the VACUUM command to remove this space.

Vacuuming is very slow. The vacuum command is essentially the same as the command line sqlite3 olddb .dump | sqlite3 newdb; mv newdb olddb. On some networked drives, vacuuming a 10MB database has been timed at over one minute. Therefore, you should avoid vacuuming whenever possible.

Some items in databases are privacy sensitive, such as deleted history items. Users have the expectation that deleting items in their history will remove the traces of that from the database. As a result, Mozilla enables the SQLITE_SECURE_DELETE preprocessor flag in db/sqlite3/src/Makefile.in . This flag causes deleted items to be filled with 0s on disk. This eliminates the need to vacuum except to reclaim disk space, and makes many operations much faster.

Zero-filling can have significant performance overhead in some situations. For example, the history service used to delete many database items at shutdown when expiring old history items. This operation is not necessarily slow, but writing 0s to disk in an "ACI" database is still slow. This made shutdown very slow because the AsyncIO thread would block shutdown ( bug 328598). Shutdown times of more than 30 seconds were seen. As a result, this bug introduced incremental history expiration eliminating the need to write many 0s to disk on shutdown.

Unfortunately, this operation cannot be controlled on a per-transaction or per-connection basis. Some operations will benefit, while others will be hurt.


由此看来，加快启动速度的同时，可能会导致关闭速度的减慢。。。。若想要提高启动速度的同时，也提高关闭速度，最好的办法就是采用FF的默认配置，然后每隔一段时间（最好一个月左右）自己清理一下数据库。使得启动的时候不会读取太多的数据，关闭的时候不会写入太多的数据。。。。

上面的链接好像也是执行VACUUM这条指令，只不过不用重启而已。。。看来有空要对VACUUM这条指令进行研究，不知道它的详细原理是怎样的。。。。

12.6M
不用刻意去减小places.sqlite的大小也可以很快的
http://mozillalinks.org/wp/2009/08/vacu ... o-restart/

默认值是180天，呵呵，也就是半年，那一起向100M的目标前进吧，

shenyixin99：刚刚又删除了5000条历史记录，places的大小减少了500K。
可见，1万条历史记录，将会使places的大小增加1M。

某些人的历史记录若达到200万条，places的大小达到200M并不为奇。
一天访问几千条，一年就足以达到200万条，呵呵。。。。大家一起向这个宏伟目标前进 回到原帖

默认值不是90天吗？