[Digikam-devel] [Bug 254033] batch queue manager should use all or more CPU cores

Jens Mueller tschenser at gmx.de
Wed Oct 13 10:35:56 BST 2010


https://bugs.kde.org/show_bug.cgi?id=254033





--- Comment #6 from Jens Mueller <tschenser gmx de>  2010-10-13 11:35:52 ---
(In reply to comment #5)
> A new Thread manager must be written to :
> 
> - Process each queue in a dedicated thread
Yes.

> - Process item in parallel. No need to wait than one item is processed to work
> on next one. We will use OpenMp at this place.
Speaking from bird eyes view, I do not think so. All filters are build on top
of dynamicthread class and that one is build on qrunnable, right? So we have to
chain the filter stack for each image into another qrunnable and execute all of
them in parallel. But I have get a deep lock at the code first.

> - Separate GUI of thread processing. Currently, GUi is used to manage the item
> and queue to process in a separate thread. This must be done in a low level.
Yes. Another problem is the chaining of output messages that refer to one
image.

> GUi must show only the result of thread processing.
Yes.

> 
> These changes will break a lots of code in BQM. i'm not sure if we can do it in
> 1.x.
I do not think that this is a simple task, so not for 1.6.

> 
> Jens, are you interrested to work with me on this subject ?
Yes, but I lack in time.

> 
> Note : before to work on this file, this one must be solved : 
> 
> https://bugs.kde.org/show_bug.cgi?id=195784
> 
> All is ready in settings to pass dedicated RAW decoding settings to queue
> processing. Only GUi must be factored with Raw import tools (settings) and
> shared with BQM.
> 
> Gilles Caulier

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Digikam-devel mailing list