https://bugs.kde.org/show_bug.cgi?id=396086
--- Comment #39 from Rafael <rafael.linux.u...@gmail.com> ---
(In reply to Jens from comment #35)
> Didn't work at first, but after changing {1..65000} to $(seq -w 1 65000), it
> worked fine.
>
> First startup with initial scanning of folders was done in ~10 seconds.
> Scanning of images - after startup - with progress bar at the bottom of the
> main Digikam window progressed with ~100 images per second, as I could see
> in the console where I started the Digikam appimge.
>
> Scanning slowed down until at "FolderB", so after roughly 65000 images, it
> took 0.5s per image (!) - so I won't finish scanning all 300'000 images
> today. Will keep you updated.
For me (in bash of OpenSUSE) that parameter for the loop worked. What's your
o.s.?
Anyway, I did (better, I'm doing) the test, but after more than 28h, it didn't
finish. There is no delay if I close and launch again Digikam, but today it
only have (I guess) scanned completely "FolderA" and "FolderB", half of
"FolderC" (29029 files) and 1580 files of "FolderD". "FolderF" is not showed.
Doesn't appear (but it exist in Dolphin). But the worst is that Digikam doesn't
show any album content (no thumbails) despite it's showing the images counter
at the end of each album. Meanwhile, Digikam is taking one CPU core to 100%.
What about your experiencie, Jen?
--
You are receiving this mail because:
You are watching all bug changes.
