[digiKam-users] raw demosaicing uses only one core

[Hans-Peter huth]

is this by intention? Component info says "Parallelized demosaicing:
Keine" (no parallel demos.) Digikam version is 6.1.0 from
Manjaro repos.

Can this be enabled by self-compiling or are there good reasons for using
only one core?

HP
--
--------- 8< -------------
Why taunt me? Why upbraid me? I am merely a genius, not a god.
(Nero Wolfe)
Meine Bilder: http://jalbum.net/a/1456383
Berge: http://jalbum.net/de/browse/user/album/1823943

[Gilles Caulier-4]

Hi,

This info just want mean that digiKam is not compiled with libgomp
support (OpenMP is used inside libraw to compute demosaicing).

This is just a packaging tune as this is optional at compile time.

Alt : use the AppImage linux bundle instead. This one is compiled with
OpenMP. 6.2.0 pre-release is here :

https://files.kde.org/digikam/

Best

Gilles Caulier

Le lun. 6 mai 2019 à 22:10, Hans-Peter <[hidden email]> a écrit :

>
> is this by intention? Component info says "Parallelized demosaicing:
> Keine" (no parallel demos.) Digikam version is 6.1.0 from
> Manjaro repos.
>
> Can this be enabled by self-compiling or are there good reasons for using
> only one core?
>
> HP
> --
> --------- 8< -------------
> Why taunt me? Why upbraid me? I am merely a genius, not a god.
> (Nero Wolfe)
> Meine Bilder: http://jalbum.net/a/1456383
> Berge: http://jalbum.net/de/browse/user/album/1823943
>
>

[Hans-Peter huth]

On Tue, 7 May 2019 08:16:48 +0200
Gilles Caulier <[hidden email]>
wrote:

> Hi,
>
> This info just want mean that digiKam is not compiled with libgomp
> support (OpenMP is used inside libraw to compute demosaicing).
>
> This is just a packaging tune as this is optional at compile time.
>
> Alt : use the AppImage linux bundle instead. This one is compiled with
> OpenMP. 6.2.0 pre-release is here :

I tested AppImage Rev. abc5f5e29ae41512f154eaea1a07b5a1a9e1f8a4. No
parallel demosaicing :(
Component info is the same as mentioned in the previous mail.

HP

>
> https://files.kde.org/digikam/
>
> Best
>
> Gilles Caulier
>
> Le lun. 6 mai 2019 à 22:10, Hans-Peter
> <[hidden email]> a écrit :
> >
> > is this by intention? Component info says "Parallelized demosaicing:
> > Keine" (no parallel demos.) Digikam version is 6.1.0 from
> > Manjaro repos.
> >
> > Can this be enabled by self-compiling or are there good reasons for
> > using only one core?
> >
> > HP
> > --
> > --------- 8< -------------
> > Why taunt me? Why upbraid me? I am merely a genius, not a god.
> > (Nero Wolfe)
> > Meine Bilder: http://jalbum.net/a/1456383
> > Berge: http://jalbum.net/de/browse/user/album/1823943
> >
> >  
>

--
--------- 8< -------------
Why taunt me? Why upbraid me? I am merely a genius, not a god.
(Nero Wolfe)
Meine Bilder: http://jalbum.net/a/1456383
Berge: http://jalbum.net/de/browse/user/album/1823943

[Gilles Caulier-4]

You are right. I restored the openMP detection with this commit :

https://invent.kde.org/kde/digikam/commit/3eb3731be5787e35dfb1101c52cf518a11191779

Gilles Caulier

Le mar. 7 mai 2019 à 19:53, Hans-Peter <[hidden email]> a écrit :

>
> On Tue, 7 May 2019 08:16:48 +0200
> Gilles Caulier <[hidden email]>
> wrote:
>
> > Hi,
> >
> > This info just want mean that digiKam is not compiled with libgomp
> > support (OpenMP is used inside libraw to compute demosaicing).
> >
> > This is just a packaging tune as this is optional at compile time.
> >
> > Alt : use the AppImage linux bundle instead. This one is compiled with
> > OpenMP. 6.2.0 pre-release is here :
>
> I tested AppImage Rev. abc5f5e29ae41512f154eaea1a07b5a1a9e1f8a4. No
> parallel demosaicing :(
> Component info is the same as mentioned in the previous mail.
>
> HP
>
> >
> > https://files.kde.org/digikam/
> >
> > Best
> >
> > Gilles Caulier
> >
> > Le lun. 6 mai 2019 à 22:10, Hans-Peter
> > <[hidden email]> a écrit :
> > >
> > > is this by intention? Component info says "Parallelized demosaicing:
> > > Keine" (no parallel demos.) Digikam version is 6.1.0 from
> > > Manjaro repos.
> > >
> > > Can this be enabled by self-compiling or are there good reasons for
> > > using only one core?
> > >
> > > HP
> > > --
> > > --------- 8< -------------
> > > Why taunt me? Why upbraid me? I am merely a genius, not a god.
> > > (Nero Wolfe)
> > > Meine Bilder: http://jalbum.net/a/1456383
> > > Berge: http://jalbum.net/de/browse/user/album/1823943
> > >
> > >
> >
>
>
> --
> --------- 8< -------------
> Why taunt me? Why upbraid me? I am merely a genius, not a god.
> (Nero Wolfe)
> Meine Bilder: http://jalbum.net/a/1456383
> Berge: http://jalbum.net/de/browse/user/album/1823943
>
>

[Hans-Peter huth]

On Wed, 8 May 2019 18:15:48 +0200
Gilles Caulier <[hidden email]>
wrote:

> You are right. I restored the openMP detection with this commit :
>
> https://invent.kde.org/kde/digikam/commit/3eb3731be5787e35dfb1101c52cf518a11191779
>
> Gilles Caulier
>

Just to confirm: the AppImage from today, Mai, 9, now uses all cores for
demosaicing, many thanks. Performance and CPU core usage is still not
optimal, but quite a bit better again.

HP

--
--------- 8< -------------
Why taunt me? Why upbraid me? I am merely a genius, not a god.
(Nero Wolfe)
Meine Bilder: http://jalbum.net/a/1456383
Berge: http://jalbum.net/de/browse/user/album/1823943