24.7 CPU Temps

Started by ProximusAl, July 26, 2024, 03:28:26 PM

Previous topic - Next topic
It may just be me, but has anyone noticed the thermals increased with 24.7?

Pre upgrade I was about 38C, and now I'm at 45C. Nothing else has changed.

I've not seen any difference in temperatures. The attached is what's been captured by Netdata for the last 2 days. The 24.7 upgrade was performed around 15:30 yesterday (indicated by the red mark).

This is also odd. Since upgrading the table reporting CPU temp under health is recording 0


Works for me fine, and as well I don't see differences in temps.

From perspective of CPU usage & resources I don't see any significant extra resource util by the new Dashboard.

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

Interesting.

I reset my RRD data and it is now working.....but temp still about 7C higher

July 26, 2024, 07:03:22 PM #5 Last Edit: July 26, 2024, 07:06:04 PM by mgl
Same here, when I remove the widget and add it again it shows the correct temp for a short time, after some time all cores (0-3) are displayed and here one core is always displayed too high, then it jumps back to only one core and then the temp is no longer correct.

"configctl system temp" shows approx. 5 degrees difference.
Which corresponds exactly to what the "old" dashboard displayed

Hey...you're right.

I ran that command on mine and it says 38C but the widget shows 45C.

I think this is a bug in the widget perhaps?

I'm seeing the same this; the widget shows different values than the command above does.
Perhaps the widget shows an average of a specific duration?

July 26, 2024, 08:31:35 PM #8 Last Edit: July 26, 2024, 08:39:22 PM by mgl
Strange is the reporting health shows the right values 39 - 41 degrees - widget shows 45- 47.
Had to reset RRD data, before it shows 0

Yes....I can confirm, health data accurate, widget is not.

I should add CPU is N100 just in case that matters 😀


July 26, 2024, 11:06:47 PM #12 Last Edit: July 26, 2024, 11:38:25 PM by MenschAergereDichNicht
I see the following:

- The widget shows 63°C
- The RRD health data shows an average of ~53°C
- "sysctl -a | grep temperature" shows 50°C
- "sysctl dev.cpu | grep temparature" shows 43°C

Not all executed at the exact same point in time but after several tries the trend is stable.

If i compare the visualization of the CPU-Widget with the output of "top" it looks also quite different. But maybe this is just the sampling intervall.

System: Celeron J6412 and thermal sensor configuration set to use the on-die thermal sensors.

I noticed that, too. I have an INTEL N5105. Before 24.7, the temperature was around 48-53°C. On 24.7, the widget shows up to 60°C.

We've always had the issue that querying the temperature had such a high resolution that a query through the GUI showed higher temps due to the processing required instead of dispatching a single command on the idle shell (while the GUI wasn't doing anything).

We may have to write a small tool to fetch the temperatures in the background away from the GUI so when the GUI query comes in it reads the actual value, not the one while the CPU is busy processing the user request..?


Cheers,
Franco