[Digikam-users] A modern auto-fix?

Gilles Caulier caulier.gilles at gmail.com
Sun May 11 13:18:43 BST 2014


4.0.0 has a lots of tool ported (not all).

Gilles Caulier

2014-05-11 13:20 GMT+02:00 Carl McGrath <cmcgrath5035 at comcast.net>:
> OK, so I read your referenced bug report - you have been busy!
>
> Will all these enhanced tools be multi-thread operation with 4.0.0, or a
> future 4.x.y?
> I guess I would expect only minor fixes between 4.0.0-rc and 4.0.0
>
> Anyway, thanks for your continued efforts - digikam is a great toolset.
>
>
>
> On 05/10/2014 04:52 PM, Gilles Caulier wrote:
>>
>> 2014-05-10 22:22 GMT+02:00 Carl McGrath <cmcgrath5035 at comcast.net>:
>>>
>>> Gilles
>>> I am running 4.0.0-rc on openSUSE, LC does seem faster.
>>> In System Monitor, when running LC,  I see Digikam using up to 30% of
>>> CPU,
>>> which on a quad-core means a bit more than one full core.
>>>
>>> Is there any config that needs to be done/enabled, or does Digikam just
>>> take
>>> what it can get?
>>
>> no. Your implementation (4.0.0-RC) use just single separated thread.
>>
>> On current implementation, this scan all cores available on the system
>> (here i7 CPU = 8 cores) and divide all operations parallelizable. Each
>> core will run a parallelized part.
>>
>> Gain depend of complexity of computation to process : between 40% to
>> 60% of time is saved.
>>
>> Gilles Caulier
>> _______________________________________________
>> Digikam-users mailing list
>> Digikam-users at kde.org
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
>
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users



More information about the Digikam-users mailing list