https://bugs.kde.org/show_bug.cgi?id=496691
--- Comment #13 from garfer <garfer1...@gmail.com> --- since this seems to be the issue 'll add some more specific details CPU: intel i5-12600KF time to find duplicates on a gallery containing 5994 images (similarity and thumbnail DBs created and updated): -- commit a07cfdb7, DB on SSD + images on HDD total time: 1min 58s peak ram usage: 1900mb HDD read (kB/s): 12572 SSD read (kB/s): 10120 -- commit a07cfdb7, DB + images on SSD total time: 22s peak ram usage: 1800mb peak HDD read (kB/s): 0 peak SSD read (kB/s): 65640 -- commit b2981ed4, DB on SSD + images on HDD total time: 2s peak ram usage: 750mb peak HDD read (kB/s): 0 peak SSD read (kB/s): 9595 -- commit b2981ed4, DB + images on SSD total time: 2s peak ram usage: 750mb peak HDD read (kB/s): 0 peak SSD read (kB/s): 9466 *the usage stats are all approximate due to the way they were gathered but fairly consistent, disk stats were taken using iostat running on 1s intervals, ram usage was taken from fastfetch from those numbers it seems that the usage of the database is consistent across versions but after commit a07cfdb7 digikam has started accessing the images themselves instead of only the DB i'm including ram stats because i also noticed a very high ram usage on the newer version when running a duplicate search on a large set of images, i think i got to over 9GB before i stopped the program, i disregarded it at the time but it might be a thing seeing some sort of cache being mentioned, please note the i didn't do any specific testing on that regard so it might be nothing -- You are receiving this mail because: You are watching all bug changes.
