https://bugs.kde.org/show_bug.cgi?id=496691
garfer <garfer1...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Resolution|NOT A BUG |---
Status|RESOLVED |REOPENED
--- Comment #3 from garfer <garfer1...@gmail.com> ---
i was wrong, the issue returns after closing and opening the program, that's to
say if i search two times for duplicates among the same set of images within
one session the first time will be extremely slow (in my test case over 10
minutes) and the second time will take under 5 seconds, if i then close and
reopen digikam it will take again over 10 minutes; in the same conditions the
previous versions of digikam always run the same search in under 5 seconds
also something i noticed is that when looking for duplicates on the newer
version i can hear digikam accessing the images on the HDD while older versions
seem to run the search using only the data on the DB without ever directly
accessing the images (i have the DBs on an SSD and the images on an HDD so it's
very noticeable)
all the previous stuff still applies but this time i'm using two databases, one
of them for the weekly appimage "8.5.0-20240831T112634" and other for the
release version of 8.5 just in case it had something to do with the new unique
file hash
--
You are receiving this mail because:
You are watching all bug changes.
