Bugzilla – Bug 14955
Scan / Look for new and changed music takes forever
Last modified: 2011-08-16 07:27:08 UTC
Running a Sony Vaio @ 1.2GHz / 1.5GB RAM With 7.3.x, looking for new music with a database of appr. 70.000 items, adding appr. 200 new files did not take longer than 25 minutes. Scanning without adding any new files usually took about 20 minutes. Now, with 7.4.x (all beta builds so far), scanning a database of 40.000 files (I did not yet add all because every scan takes so long) takes about 40 minutes (1 minute / 1.000 unchanged items). Adding new music (say, 400 files) takes appr. 20% longer. The progress indicator now counts all files. With 7.3.x, it used to only count added files which in my eyes made a lot more sense for a scan for new & changed music. The scanner engine should be able to tell without huge mysql operations which files were added/changed. And then ONLY scan the new files. It seems that for all unchanged items, the scanner still goes through tags and validates them in the database? Anywhose, the whole scan for new & changed music now takes much - MUCH! - too long compared to older SB Server versions (7.3.x and before).
QA to verify with 7.5.x, as the scanner code is being re-written and should be MUCH faster.
Created attachment 6322 [details] Library Scan for New Music - Screenshot
(In reply to comment #2) > Created an attachment (id=6322) [details] > Library Scan for New Music - Screenshot I added 19 new albums (each with cover art). The scan took quite a bit.
Adding the TinySC keyword so that we can look out for this on that project, too.
Changing priorities due to management guidance.
Wow. With 7.5.6, a whole new scan on 80.000 files took 2hrs. I'll see today how long a scan for updated files takes. This is a big improvement: No scanner.exe errors since ages. I think I might start to use my squeezebox on my home library again.