[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2022-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=435564

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Version Fixed In||7.5.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=435564

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #12 from caulier.gil...@gmail.com ---
As it's an hardware problem i close this issue now.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-13 Thread hannesj
https://bugs.kde.org/show_bug.cgi?id=435564

--- Comment #11 from hann...@hot.ee  ---
Thanks for the answers. I understand that the search for similarities must work
that way.
Hannes

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-12 Thread Bruno Abinader
https://bugs.kde.org/show_bug.cgi?id=435564

Bruno Abinader  changed:

   What|Removed |Added

 CC||brunoabina...@gmail.com

--- Comment #10 from Bruno Abinader  ---
>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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=435564

--- Comment #9 from caulier.gil...@gmail.com ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-10 Thread hannesj
https://bugs.kde.org/show_bug.cgi?id=435564

--- Comment #8 from hann...@hot.ee  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=435564

--- Comment #7 from caulier.gil...@gmail.com ---
https://en.wikipedia.org/wiki/Operating_temperature

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=435564

--- Comment #6 from caulier.gil...@gmail.com ---
https://www.buildcomputers.net/cpu-temperature.html

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=435564

--- Comment #5 from caulier.gil...@gmail.com ---
https://en.wikipedia.org/wiki/Computer_cooling

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=435564

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #4 from caulier.gil...@gmail.com ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=435564

--- Comment #3 from Maik Qualmann  ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=435564

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

2021-04-10 Thread hannesj
https://bugs.kde.org/show_bug.cgi?id=435564

--- Comment #1 from hann...@hot.ee  ---
Created attachment 137464
  --> https://bugs.kde.org/attachment.cgi?id=137464=edit
Open Hardware Monitor -clock bus speed

-- 
You are receiving this mail because:
You are watching all bug changes.