Bug 346363

If I start servicing my databases, I experience always very slow progress. 
"Servicing" about 900 new pics takes time for hours and hours seemingly not to end up at alll :-(

In this case, I just seacrh for new pics and refresh previews.

My motherborad runs an powerful quadcore.
When checking put for reasoins, I found, that didiKam just engages 25% of my CPU(s). 
For this reason, I conclude, that digiKam doe _not_ use all CPUs right now.

This is a severe handycap, as it make digiKam appear slowly.

 

Reproducible: Always

Steps to Reproduce:
1. Please take care, that digiKam runs all CPU a machine provides and/or introduce an intelligent CPU management, a user can pre-select about the number of engaged CPUs.
2.
3.

Actual Results:  
digiKams performance is not satisfying at all: maybe you'll check ourt GIMP concerning this feature or HUGIN, which applyies graphic-card-capabilities.

Expected Results:  
digiKam should work and run on the level of nowadays programs. 
It seems to be old fashioned to just use one single CPU.

Because of the slowliness, whicgh forces the user to wait terribly long, this is a failure of major importance!!!