cpd73 wrote: > Sorry, not really. The bliss-analyser code is pretty simple - just > collecting a list of files then asking bliss-rs to analyse them.
The scan completed after 1hr43m, with no errors. While it was running it was using about 2.5% CPU and 12 threads. I've just restarted it with the path set specifically to that 'Lossy' folder, and it's started up with ~500% CPU and ~30 threads, so clearly it's going to complete faster. I wonder if it's something to do with the way the tasks are split between the available cores. Does the core allocation happen before the folders are skipped due to .notmusic, or afterwards? If before, and all the allocated folders on some cores turn out to be skipped, that would explain why it's using fewer resources and running slower. ------------------------------------------------------------------------ chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=116068 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
