[Digikam-devel] [digikam] [Bug 198063] SCAN : digikam startup is extremely slow
Paul Sommer
nl at paul-sommer.de
Thu Oct 2 04:01:29 BST 2014
https://bugs.kde.org/show_bug.cgi?id=198063
Paul Sommer <nl at paul-sommer.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nl at paul-sommer.de
--- Comment #38 from Paul Sommer <nl at paul-sommer.de> ---
Martin,
How did you manage to get that improvment in starting speedup?
I am using digikam 4.3 now with 40.000 images on a nfs share and a local
database on a ssd drive and it still takes about 25 seconds to collect the
images. During that time Digikam reads AND WRITES 500 kb/sec to the network
(why does it write at all with a local database??)
Even worse: directly after the start of digikam the current album is scanned
again. This again takes 3 to 15 seconds depending on the album size and if
Digikam had crashed (which happens every couple of minutes since I switched to
64bit Kubuntu).
Why has the "scan for new images on startup" switch been removed?
It's so frustrating to see the "anti usability dogma" spreading all over KDE
since a couple of years :(
So, for me this issue is not fixed at all.
If I can provide any further infos on that matter, please let me know.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Digikam-devel
mailing list