mherger wrote: > - VACUUM is being run on library.db and persist.db during a wipe & > rescan. persist.db only is VACUUMed if its fragmentation has reached a > certain level though (20%).
Do you turn on auto_vacuum during the scan, do a vacuum before scanning, or do a vacuum after scanning? Why not also do the remaining databases? The thing I dislike about this approach is that if everything in LMS worked as it should (i.e. if there were no scanning bugs or bugs that cause the database to become inconsistent or corrupted) users should never have to run a full rescan. Having to do so to maximize performance is not the best strategy, IMO. For the users for whom this will do the most good, that full rescan may take hours due to very large libraries or very slow hardware. > - I've added a third "highmem" option: Default, High, Maximum. The third > > option would use _lots_ of memory if needed (up to 500MB per database), > > but only as much as needed, of course. It might be the best option for > most users who are running LMS on PC class hardware. Is the max buffer size per SQLite database or is there just one buffer for the entire LMS application? ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=101469 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
