Bug 435564 - The similarity finder uses about half the CPU clock speed
Summary: The similarity finder uses about half the CPU clock speed
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Maintenance-Similarities (show other bugs)
Version: 7.3.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-10 07:56 UTC by HJ
Modified: 2022-01-02 10:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.5.0


Attachments
Open Hardware Monitor -clock bus speed (3.81 MB, image/jpeg)
2021-04-10 07:59 UTC, HJ
Details

Note You need to log in before you can comment on or make changes to this bug.
Description HJ 2021-04-10 07:56:27 UTC
SUMMARY
the similarity finder uses about half the CPU clock speed

STEPS TO REPRODUCE
1. CPU clock speed measurement
2. High performance mode 
3. Use  left-side similarity finder

OBSERVED RESULT
CPU clock speed is 
about half of the maximum

EXPECTED RESULT

Max CPU speed

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 HJ 2021-04-10 07:59:30 UTC
Created attachment 137464 [details]
Open Hardware Monitor -clock bus speed
Comment 2 Maik Qualmann 2021-04-10 09:33:18 UTC
Well, digiKam cannot control the hardware clock directly. It would be to test what would happen if we gave the tasks a higher priority. However, there are also a lot of database accesses and these relieve the required CPU core again in the meantime. But do we really want to make the computer inoperable when digiKam is running?

Maik
Comment 3 Maik Qualmann 2021-04-10 09:44:00 UTC
I find your CPU temperature critical, even an Intel CPU should better stay below 80°C. The 80-95°C are possible, but should be avoided.

Maik
Comment 4 caulier.gilles 2021-04-10 10:02:46 UTC
And Intel, as other CPU have temperature security. 

80° is the limit for a safe public core uses. Higher values make CPU unstable and possible internal logic transistors destruction.

Military and high critical use (as space module) electronics can be overloaded to 120°C but it's require more tests in build process and this very expensive.

So i recommend to check the freeze system for your CPU. Typically the thermal paste, the cpu fan, etc...

Gilles Caulier
Comment 5 caulier.gilles 2021-04-10 10:06:06 UTC
https://en.wikipedia.org/wiki/Computer_cooling
Comment 6 caulier.gilles 2021-04-10 10:07:21 UTC
https://www.buildcomputers.net/cpu-temperature.html
Comment 7 caulier.gilles 2021-04-10 10:08:43 UTC
https://en.wikipedia.org/wiki/Operating_temperature
Comment 8 HJ 2021-04-10 15:48:28 UTC
It is strange that during the operation of DK similarity and other resource-intensive processes, the CPU clock speed decreases from the maximum to 54-75%. At the end of the process, it rises to the maximum. Testing was performed with MS Edge open at the same time.
This also means other concurrent programs must be able to handle at slowed CPU clock speeds.
Comment 9 caulier.gilles 2021-04-10 15:52:52 UTC
But it's clear : as Maik said, the CPU temperature exceed the limit and CPU security turn on to limit clock and de-facto the temperature.

To resume : You have a problem with your CPU cooling. Check your system.

Gilles Caulier
Comment 10 Bruno Abinader 2021-04-12 09:09:45 UTC
From the hardware monitor screenshot, we can see all four cores are at 100%, thus operating as expected. As Maik mentioned, it is not digiKam's responsibility to select which CPU clock speed your OS wants to use, we can only request from the OS to provide us with threads for the application to use.
Comment 11 HJ 2021-04-13 15:07:18 UTC
Thanks for the answers. I understand that the search for similarities must work that way.
Hannes
Comment 12 caulier.gilles 2021-04-14 07:37:18 UTC
As it's an hardware problem i close this issue now.

Gilles Caulier