24.7 CPU Temps

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

Previous topic - Next topic
You're ignoring the underlying problem of both mine and maxus' concern regarding the higher CPU utilization, and higher temps being a symptom of it.

If it were *just* a widget reporting higher temperatures, I wouldn't be so annoyed with your responses... But a major increase in utilization correlates with what we're seeing.

I'm also well aware of what my specs are as I'm seeing spikes of temps above 70C, which is the maximum for my processor. Right now it's averaging 60C.

August 28, 2024, 12:52:17 AM #46 Last Edit: August 28, 2024, 12:56:15 AM by doktornotor
Yeah, I'm ignoring underlying non-existent problems such as CPU being used for computing and running at whopping 60C. This is in the same area such as complaints about memory being used e.g. for caching, instead of being wasted. That's another evergreen.

Not sure for which CPU there's 70C max but if you have such processor, then indeed your cooling is inadequate and needs improving to prevent unexpected shutdowns. Adequate cooling is such that it keeps CPU stable and within its operating specs at 100% load of all cores, for prolonged time. You can do such tests yourself even on OPNsense:


pkg install stress-ng

If you think an unexplained 25x increase in CPU utilization resulting from an update is a non-existent problem, then there is no hope in discussing this rationally.

It's very clearly a flaw and it explains why more heat is being generated.

Perhaps start a new topic providing some real information, using tools such as top about your 25x higher CPU usage (compared to unknown base).

@irrenarzt (how come to choose such a name?!?)

Which services are you using? Suricata or alike maybe?
kind regards
chemlud
____
"The price of reliability is the pursuit of the utmost simplicity."
C.A.R. Hoare

felix eichhorns premium katzenfutter mit der extraportion energie

A router is not a switch - A router is not a switch - A router is not a switch - A rou....

Quote from: irrenarzt on August 28, 2024, 01:01:36 AM
If you think an unexplained 25x increase in CPU utilization resulting from an update is a non-existent problem, then there is no hope in discussing this rationally.

It's very clearly a flaw and it explains why more heat is being generated.

I have an N100 and have seen no increase in CPU usage nor CPU temperature, it's always well under 60 so it's clearly not a flaw and doesn't explain anything.

As Chemlud said, what else is going on with your device?

August 28, 2024, 10:23:04 AM #51 Last Edit: August 28, 2024, 10:27:40 AM by doktornotor
Quote from: wogman on August 28, 2024, 09:52:44 AM
I have an N100 and have seen no increase in CPU usage nor CPU temperature, it's always well under 60 so it's clearly not a flaw and doesn't explain anything.

As Chemlud said, what else is going on with your device?

The pattern here seems to be

a/ a new version is released on top of new major FreeBSD version, with tons of rewrites (such as the dashboard) People notice that things changed and scream "oh noes, it uses more CPU/RAM/beer in my fridge vanished and my cat got ill after upgrade! On the previous version it was just fine, CPU was barely being used. The new one sucks!" "640KB of memory ought to be enough for anybody!"

b/ users that have some runaway process running or some quirk in their setup (which may or may not be related to the upgrade at all) jump on the bandwagon and keep adding completely non-specific complaints about their fringe issue to those topics.

Wash, rinse, repeat...

No, 24.7 has NOT increased CPU usage 25 times... Start your own topic for debugging particular issue you are observing and provide some basic info.

No, CPUs don't burn at 60C. They've not been burning for years even without heatsink.

And as also noted above. Do not base your cooling on the assumption that your CPU will be unused. You can always hit a situation when some bad process will tax your CPU cores for tens of minutes / hours due to a bug, suboptimal code or by simply you configuring something your HW is not capable of handling reasonably. Things like IPS, netflow, or huge DNS blocklists getting parsed by the python code for hours come to mind.


Quote from: doktornotor on August 28, 2024, 10:23:04 AM
...
The pattern here seems to be

a/ a new version is released on top of new major FreeBSD version, with tons of rewrites (such as the dashboard) People notice that things changed and scream "oh noes, it uses more CPU/RAM/beer in my fridge vanished and my cat got ill after upgrade! On the previous version it was just fine, CPU was barely being used. The new one sucks!" "640KB of memory ought to be enough for anybody!"

b/ users that have some runaway process running or some quirk in their setup (which may or may not be related to the upgrade at all) jump on the bandwagon and keep adding completely non-specific complaints about their fringe issue to those topics.

Wash, rinse, repeat...
....


...and once a week a thread with "out-of-state traffic" and some totally insane newbie fw rules. :-) Daily bussiness. Keep calm and post on. ;-)
kind regards
chemlud
____
"The price of reliability is the pursuit of the utmost simplicity."
C.A.R. Hoare

felix eichhorns premium katzenfutter mit der extraportion energie

A router is not a switch - A router is not a switch - A router is not a switch - A rou....

Quote from: chemlud on August 28, 2024, 10:45:57 AM
...and once a week a thread with "out-of-state traffic"

Recall debating this a year or so ago on Github. Put the flags there to be displayed directly with the logs, not hidden under the i. I guess I should revive the request.

Point is: Beginners won't get it, no matter which text you provide. Has allready been adapted in the past. As long as they don't know/care for TCP flags and the basics of the protocoll: Same question will come up again and again.

Learning curve is steep in the beginning. But one soul saved from the plasic box router faction is worth posting sensible replies to beginner questions. Sticky threads might be used to be linked in "standardized" replies, maybe...
kind regards
chemlud
____
"The price of reliability is the pursuit of the utmost simplicity."
C.A.R. Hoare

felix eichhorns premium katzenfutter mit der extraportion energie

A router is not a switch - A router is not a switch - A router is not a switch - A rou....

Quote from: chemlud on August 28, 2024, 10:58:21 AM
Point is: Beginners won't get it, no matter which text you provide.

Indeed, but it makes things obvious without having to ask them to click somewhere. I find this annoying as well, having it visible helps to visually spot / filter out irrelevant noise.

Quote from: chemlud on August 28, 2024, 10:58:21 AM
... But one soul saved from the plasic box router faction is worth posting sensible replies to beginner questions.

LOL that's a good one !

I too do not see any increasing temp level on both of my units, Dell sd_wan Edge 860 or the tiny Thinkcentre m920q. Cpu temps hover around 46-50C degr as before on v24.1

I am not running Suricata. The only optional services I'm running are CrowdSec and Unbound, of which neither appear to be the crux of the issue as their utilization is the same as before. There are no runaway processes, nor indicators in my logs. My configuration between 24.1 and 24.7 is identical outside of what changed from the update.

This exact problem is also being noticed and shared outside of this particular forum. Here is another example from a user on Reddit that has a screenshot of the same trend myself and maxus have seen after the update:
https://www.reddit.com/r/opnsense/comments/1f13bkk/weird_cpu_utilization_since_2472/

Instead of irrationally deriding the problem as an issue with my forum post count, lets try acknowledging that multiple people are sharing the exact same data point of historical CPU utilization showing steep increases following the 24.7 update with no other configuration changes. In each case CPU utilization skyrockets immediately after the update (as obviously shown in the graphs) and maintains a significantly higher average than under 24.1.

I was seeing other similar posts from people prior to discovering I had the same problem. I didn't notice any obvious performance or operational impacts from normal use, and bought into the initial narrative that higher CPU temps were simply a result of how the new widget is reporting. However, after seeing repeated claims of higher CPU utilization with 24.7 I looked into my own health reports, and realized I have the same vertical cliff face of dramatically increased usage and load averages. Now that I'm seeing multiple people with the same problem, I'm not inclined to believe CPU temps are anything less than a symptom of a greater flaw.

...let's also acknowledge that multiple users have no problem at all. So...
kind regards
chemlud
____
"The price of reliability is the pursuit of the utmost simplicity."
C.A.R. Hoare

felix eichhorns premium katzenfutter mit der extraportion energie

A router is not a switch - A router is not a switch - A router is not a switch - A rou....

I am not ignoring that, as I'm well aware that hardware differences and such can impact differently just like with any other piece of software. Any legitimate testing takes into account different platforms.