I also knew that vacuum is a good thing and can tell is realy worth to do (even if a dont rescan always drop db and do a freshscan). The "new" feature to look @ the db filesizes via webgui is something "some" not so experienced Endusers will kiss your feets ;-)
The auto_increment is not about performance, but about disk space recovery only. There's even a chance that it would harm performance, due to increased fragmentation. Only the full vacuum does re-organize the file internally to clean up fragmentation. The plugin's UI is probably a bit misleading, as what is reported as "fragmentation" actually is the percentage of unused disk space occupied by the db file.
I guess that the performance improvement you've seen wouldn't become reality with enabling auto_vacuum only. But I still consider it an option for the db files which change a lot (caches).
-- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
