Summary: | align_image_stack and enfuse use only 1 CPU core if called by digiKam plugin, 4 CPU core on command line | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Frerk Meyer <frerk.meyer> |
Component: | Plugin-Generic-ExpoBlending | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, metzpinguin |
Priority: | NOR | ||
Version: | 6.3.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/kde/digikam/commit/bdada4d927635f4aa5ee9579a2964a00382eb87c | Version Fixed In: | 7.0.0 |
Description
Frerk Meyer
2019-11-09 12:52:05 UTC
from the Enfuse Help: ---- The OMP_NUM_THREADS environment variable sets the number of threads to use in OpenMP parallel regions. If unset Enfuse uses as many threads as there are CPUs. ---- If the variable is not set, all available CPU cores will be used. I can confirm that here on openSUSE Tumbleweed, with me all CPU cores are used. Gilles, can you do a test under Mageia? Maik I only introduced the environment variable OMP_NUM_THREADS after I noticed that only 1 core was used without. It was my try to remedy the situation. So the bug was there on my machine without any environment variables with 'OMP' set. It may be specific to LEAP 15.1 or to my machine. But OMP_NUM_THREADS influences both, align_image_stack and enfuse if called from the command line as expected. Maik, yes i confirm, same behavior under Mageia... Gilles Git commit bdada4d927635f4aa5ee9579a2964a00382eb87c by Maik Qualmann. Committed on 09/11/2019 at 17:39. Pushed by mqualmann into branch 'master'. set OMP_NUM_THREADS environment variable FIXED-IN: 7.0.0 M +2 -1 NEWS M +10 -2 core/dplugins/generic/tools/expoblending/manager/expoblendingthread.cpp M +10 -1 core/dplugins/generic/tools/panorama/tasks/commandtask.cpp https://invent.kde.org/kde/digikam/commit/bdada4d927635f4aa5ee9579a2964a00382eb87c (In reply to Maik Qualmann from comment #4) Hello Maik Qualmann, Many thanks for this blazing fast response. I hope this will solve it, cant wait to try 7.0.0 then. Frerk |