[Digikam-devel] [Bug 300293] when starting digiKam, it takes about 5 minutes

Andi Clemens andi.clemens at googlemail.com
Sat May 19 13:05:31 BST 2012


https://bugs.kde.org/show_bug.cgi?id=300293

--- Comment #3 from Andi Clemens <andi.clemens at googlemail.com> ---
I can confirm this, digiKam is not usable with bigger image collections.
I created a little test program for generating small images (attached to this
bugreport).
When I create the test images and start digiKam (say 100.000 images, 1000
images in each folder), digiKam seems to take more than 8 hours to scan all the
images (I stopped at 20% after 2 hours).
The UI is visible, the "scan collection task" is running, but it is so damn
slow.
I commented out the slow code (ImageScanner::scanFromIdenticalFile() always
returning true) and digiKam was ready after 3 minutes, but I needed to kill the
process because it wasted more than 2.5 GB RAM! I don't know what happened but
after the scan finished, it started to increase memory usage like crazy.

We seem to have big issues with bigger image databases here... btw. I was using
the SQLITE backend.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Digikam-devel mailing list