Bronx wrote: > I uploaded the library.db with all 45 playlists some minutes ago. > Additionally the playlist files. When sorting the playlist-files by size > I did a rescan with all the playlists up to and with size 527 KB and > this rescan ended error free. Afterwards additionally with playlists up > to size 1 MB, this rescan was prematurely terminated when building > fulltext index 4. It is not clear to me whether this is due to the sum > of all playlists or to a single one. So on the other hand it is clear > that not the playlists with a size of more than 1 MB alone lead to the > error. That's all I can help with at the moment.
I've committed a change which... looks too good to be true! It brought down FTS indexing time from somewhere around 45 minutes to about 3 minutes. Scanning your 20k playlist previously took about 16 minutes alone, and memory consumption spiked around 9GB. Now it takes seconds, and memory stays around 1GB (with memory set to Maximum). It's late. Maybe I'm missing something obvious. So please give the search feature using FTS some thorough testing! Oh: you'll have to rescan your collection to make this work (no wipe required). Michael "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!" (LMS: Settings/Information) ------------------------------------------------------------------------ mherger's Profile: http://forums.slimdevices.com/member.php?userid=50 View this thread: http://forums.slimdevices.com/showthread.php?t=114928 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
