Initial scan taking too long [#21916]

[ruebennase56]

ruebennase56: Can you please generate new debug log for me with rescan of files (on your current installation, where you experience slow rescans - i.e. scans of files already present in your DB). Note, that with DbgView running you cannot measure time, because logging slows things down a lot. Test on some folder with many files, where there was ideally no change, so rescan should be very fast. Currently I am slightly lost and have no idea, what should slow things down for you in such situation. Thanks.

I logged a rescan of about 5.000 files of my collection:
https://1drv.ms/u/c/bae5db40241ac824/IQ ... Q?e=50InLf

To clear things up:
Build 3209
Gigabyte Eagle Ice B850 Motherboard
Ryzen 5 9600x
Systemdrive: Samsung SSD 9100 Pro (PCIe5)
Datadrive: Raid1 (WD Red)

A rescan of my whole collection (60.000 flacs) will last about 45min (Build 3184 needs less than 1 min)
The rescan with only 5.000 files needed with DbgView running 3:15min (without 2:30)
Maybe it is an issue, I still have an installation of MM4 in a different drawer.

Besides my PC, I have a HP convertible. On this setup all flacs are on a NAS and the HP is connected via WiFi7.
In this case a complete rescan will take 2:30 hours.

And what is Vanilla 3209?

[MiPi]

ruebennase56: by "Vanilla 3209" is meant separate portable clean installation. You can install last version (3209) as portable to some empty folder, run it, set the same preferences of scanning in Options - Library, scan your 5000 files and then restart MM and try rescan, whether this time it will be different. To test, whether it is related to something in your old installation (not present in clean version).
How big is your MM5.DB file in your old installation? You can also try to run optimization (File - Manage database - Maintenance - Optimize database)
In case you make us Dbg log, please run DbgView first, and then MM5. Your log shows only part of information otherwise and it is harder to analyze, thanks.

[ruebennase56]

MM5.db has after optimization the size of 233MB.

So I did a portable installation of 3209 and didn't import any settings from an old installation and used the default preferences.

Initial scan needed 4min, the rescan 2:30min.
https://1drv.ms/u/c/bae5db40241ac824/IQ ... E?e=4bziHf

I hope this will help

[ruebennase56]

I found the reason why its so slow.
I have in every drawer the artwork for that album. Usually only the cover as a JPG size 1400x1400. When i delete these 300-350 jpgs the rescan only takes 5sec.
https://1drv.ms/u/c/bae5db40241ac824/IQ ... A?e=tSWzSw

[MiPi]

Thanks! I was just prepared to try the same, as from your last log it looked it is somehow caused by the artwork files.
It should not last so long anyway, I will check it.

[SusicMnob]

I do have a massive library but it takes a LOT longer than it used to..running on build 2024.2.1.3206.

Scans used to complete in under 3-4 minutes are now taking close to 10 minutes. The underlying hardware has not changed.

Just curious if there was a scanning behavior change or if its just my library has hit some limit where its just going to be what it is.. which is fine as that would be expected behavior for a library with 155K + songs.

[MiPi]

The main problem was with libraries containing many linked artworks saved to files. Such were still not handled correctly during rescans in the last builds, including 3209, and were slowing down every rescan a lot, should be ok in the next build.

[SusicMnob]

Excellent sorry I should have searched more before posting...thanks for the update!

[SgtPepperman]

Wow, what an improvement on 3210!
Congratulations!!!!

[rusty]

rubennase56 / SusicMnob,
Can you confirm that the fix in 3210+ works for you as well?
Thanks!
-Rusty

[SusicMnob]

Scanning now is back to where it was OR better. Scans are completing now in rough 2:30-3 minutes for a file system that's got 155K tracks across just under 13K album folders.

So its looking great now - thank you!

[ruebennase56]

Many thanks, the scans are as fast as they used to be.