Phil Meyer;209686 Wrote: > I've noticed that a custom scan is now taking a little while to run now > (5 minutes), so I've turned off the automatic refresh at startup. I > can hear the HD chattering away during the rescan. > Is it SlimServer startup that takes longer time ? Is it the "Refresh custom scan data at startup" option in the Custom Scan section in Server Settings/Plugins you disabled ?
If this is the case, the problem is not rescanning. It doesn't perform a rescan at startup, it only syncronize the track identifiers with the paths. As an example, if you perform a SlimServer rescan, a specific track will often get a new track id even if the path is the same as before. What Custom Scan is doing in the refresh operation is updating the track id in the Custom Scan information to the correct one based on the path (or musicbrainz tag). If this operation is starting to take 5 minutes, we have a problem. It should be fairly fast, maybe a few seconds or maximum a half minute. The cause of this could be: 1. I've added some new indexes in the database, this could slow down updates a bit. 2. The change of the url field to support 511 characters. 3. The Mixed Tag module makes the table contain at least the double amount of data. If would help if you tried to enable debugging in the Custom Scan section of Server Settings/Plugins and then restarted SlimServer with automatic refresh at startup enabled. Then post the log, you should see a number of log messages that begins with "CustomScan" during the refresh operation, it also shows how long each part of the refresh operation takes. Phil Meyer;209686 Wrote: > I would guess though that Custom Tag is the main culprit though, as it > has to read all files for the extra tag info? If it's a "look for new > and changed music" rescan, does it only read the tags of files that > have been detected as new or changed, or is it reading the whole > library? > > Is it meant to do a custom scan refresh when I do a "look for new and > changed music" slimserver scan? I only ask because the option says > "Enable in automatic and full scans".The option is named incorrectly, it also > rescans due to "look for new and changed music". But as I said before, if the problem is at SlimServer startup, it doesn't actually read any files, it just synchronizes the track id's. I haven't found any way to detect exactly which files are new/changed, so currently CustomScan always rescan all files in the library. The Custom Tag scanning module should take a lot longer than the Mixed Tag module exactly as you suggest. If you don't think this is the case, I would appreciate if you could send me a SlimServer log with CustomScan debugging enabled during scanning operation. -- erland Erland Isaksson 'My homepage' (http://erland.homeip.net) 'My download page' (http://erland.homeip.net/download) (Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse, Custom Scan, Custom Skip, Multi Library and RandomPlayList plugins' (http://wiki.erland.homeip.net/index.php/Category:SlimServer)) ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=36226 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
