https://bugs.kde.org/show_bug.cgi?id=464769
--- Comment #9 from worthingto...@yahoo.com --- I'm not sure if you will be able to identify a bottleneck with this information but I captured the entire log file for a scan that took 81 minutes to complete. I scanned 12,348 jpg images and they are all numbered sequentially starting with 00001.jpg. In the log file I calculated the finger-print scan time between each 25% of the total files. Below was the results. 00001.jpg - 03087.jpg = 1 minute 03088.jpg - 06174.jpg = 8 minutes 06175.jpg - 09261.jpg = 23 minutes 09262.jpg - 12348.jpg = 49 minutes I did find a way to perform a finger-print scan on all 12,348 files in less than 6 minutes using the process below. 1. Launch digiKam with an empty collection 2. Drop files 00001.jpg - 03087.jpg in the collection 3. Go to maintenance Check "Scan for new items", "Rebuild Finger-prints" & "Scan for changed or non-cataloged items (faster)" The scan takes a little over 1 minute to complete 4. Close digiKam and relaunch 5. Drop in files 03088.jpg - 06174.jpg in the collection 6. Go to maintenance Check "Scan for new items", "Rebuild Finger-prints" & "Scan for changed or non-cataloged items (faster)" The scan takes a little over 1 minute to complete 7. Repeat these steps for the next two groups of files you'll have all the finger-print scanning completed in under 6 minutes. I'm not seeing digiKam consume a lot of RAM on the PC but it must be bogging down with cache or something that makes it slow down the longer the process runs. Closing and relaunching the application seems to resolve that issue. -- You are receiving this mail because: You are watching all bug changes.
