Haven’t been using Digikam in a few month and a few days ago I noticed that it has become so slow that it is almost unusable. There has been quite a few updates since it was fast so I have absolutely no idea what may have caused this.
When I clicking on an album folder, containing a few pictures, Digikam uses 3 or 4 of my 8 logical CPU’s for several seconds during which time it is unresponsive. I have 8 GB of memory with a 35% usage.
I run Digikam 3.2.0 on oS 12.3/KDE 4.10.5 and it is quite spiffy, so your problem is not wide spread(IMHO).
You might try a post on the Digikam forum, where many issues specific to various plug-ins are discussed.
Did you find anything out or has the problem cleared up for you? I am currently having the same problem here after the recent upgrade to KDE 4.11 and also at the same time kernel 3.11 so it is hard to tell what/which thing caused the problem. The cpu usage shoots up to 80% just to move the thumbnails around and the interface becomes pretty useless.
anika200 wrote:
>
> gugrim;2576614 Wrote:
>> Thanks, I’ll try that.
>
> Did you find anything out or has the problem cleared up for you? I am
> currently having the same problem here after the recent upgrade to KDE
> 4.11 and also at the same time kernel 3.11 so it is hard to tell
> what/which thing caused the problem. The cpu usage shoots up to 80% just
> to move the thumbnails around and the interface becomes pretty useless.
>
>
openSUSE 12.3 typically keeps multiple kernels. You can switch to
another kernel from boot menu ==>Advanced etc… That might tell
whether the fault is with KDE or kernel.
GNOME 3.6.2
openSUSE Release 12.3 (Dartmouth) 64-bit
Kernel Linux 3.7.10-1.16-desktop
I think I figured it out, SpiderOak + Digikam = Slow.
I have SpiderOak backing up my pictures folder and it seems to conflict with Digikam’s digikam4.db and thumbnail files. SpiderOak grabs them right away for backup and this seems to be causing some problem, if I quit SpiderOak digikam works fast as expected. I did just upgrade spideroak recently so maybe they changed something on there end, seems odd though.