Now that's interesting. How do scan times compare? Because I thought that "max" would greatly improve scan times for what I considered large collections (>50k :-)).
The good news is that the analyse part seems to run fine (and that's the important part!). Only the vacuum is causing problems. I reviewed the code, and it's indeed not using disk space for temporary storage, but RAM if the db memory parameter is set to high. With a file size of 2.8GB that would use a lot of memory. Yet I'd expect it to work. Maybe it would be worth to add some sanity checking, eg. not use memory for this call if the table size was a gigabyte or more. Unfortunately on Windows you can't easily modify the code to run a test. I've therefore created a custom build which does use disk rather than memory for the vacuum call. Could you please give it a try, set memory usage to maximum, and try again? http://downloads.slimdevices.com/nightly/7.9/sc/6b2d6a02baaa957d48e544371c4bab45db4647bd/LogitechMediaServer-7.9.2-1527843561.exe Michael http://www.herger.net/slim-plugins - Spotty, MusicArtistInfo ------------------------------------------------------------------------ mherger's Profile: http://forums.slimdevices.com/member.php?userid=50 View this thread: http://forums.slimdevices.com/showthread.php?t=109093 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
