The vacuuming makes a big difference to custom browse using custom scan
Did you check the file sizes before and after vacuum?
I've been running with a buffer of 100MB. It seems that even custom scan times are considerably improved, from around 3 hours for a full scan to about 2 hours. Can this be my imagination?
Did you only change the buffer size? I've seen reports of both, changing it to to worse and the better... but I thought it wouldn't have any impact on the scan at all, as the buffer size is not applied in the scanner :-).
As I did see some slower scanning with larger buffers, I'll have to investigate this further.
I tried with and without the indexes and can't say I've notice any difference (and I assume they get rebuilt anyway after a full rescan).
No, they are not rebuilt on a rescan. You'd have to delete the library.db or use the button in this plugin.
One question: Does the auto-vacuum setting 'stick' or not? I haven't done enough trials to quite understand how this is expected to work. If I tick it and Apply, the tick disappears.
Yeah, that UI isn't really clear. Quite obviously I didn't pay much attention to it. The plugin started as a simple UI for myself to enable/disable auto_vaccum. I didn't think it would evolve from there...
-- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
