Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
24.7 Production Series
»
24.7 CPU Temps
« previous
next »
Print
Pages:
1
...
4
5
[
6
]
Author
Topic: 24.7 CPU Temps (Read 7091 times)
meyergru
Hero Member
Posts: 1622
Karma: 163
IT Aficionado
Re: 24.7 CPU Temps
«
Reply #75 on:
September 02, 2024, 11:31:01 am »
Sorry, just wanted to help, not fight. Good luck to find the problem.
Logged
Intel N100, 4 x I226-V, 16 GByte, 256 GByte NVME, ZTE F6005
1100 down / 440 up
,
Bufferbloat A+
meyergru
Hero Member
Posts: 1622
Karma: 163
IT Aficionado
Re: 24.7 CPU Temps
«
Reply #76 on:
September 02, 2024, 12:07:45 pm »
On a side note: in /usr/local/etc/filter_tables.conf, you will find <ttl> (time-to-live) tags. For me, all GeoIP rhythms seem to be 86400. If they are at 1 minute for you, that would explain it. You can look at the last change times in /var/db/aliastables to find out which alias is causing this.
Also, there is an undocumented tag <updatefreq> in config.xml, which is probably translated into <ttl>, if set. IDK how that was modified if it is not exposed in the GUI, but who knows?
All I can say is that calling update_tables.py manually takes 4 seconds here but modifies only a few aliases. I imagine that processing of geoip aliases takes a lot longer, but in my case, this is done once per day only.
Logged
Intel N100, 4 x I226-V, 16 GByte, 256 GByte NVME, ZTE F6005
1100 down / 440 up
,
Bufferbloat A+
irrenarzt
Newbie
Posts: 16
Karma: 0
Re: 24.7 CPU Temps
«
Reply #77 on:
September 02, 2024, 09:07:07 pm »
I apologize if I sounded argumentative, was just trying to relay what I'm seeing. I genuinely only take issue with one person in this thread.
One note, I'm currently limited to what I can access via web GUI...
I checked my config.xml and <updatefreq> was only set for one 1 alias (not the Geoblock), of which I updated it so it's no longer set either... That had no impact, however.
Playing with Geoblock further, I have to get the number of current table entries below 100,000 (only 1/10th of the Geoblock list) for there to be any impact to temps and utilization.
I'm also curious about what exactly is happening when update_tables.py runs and the task it's performing, since it's not actually updating the aliases. If it were, I assume I'd see changes to the "Last updated" timestamp everytime it runs. However, the time stamp is only updating once a day based on Cron schedule.
Logged
MenschAergereDichNicht
Full Member
Posts: 108
Karma: 3
Re: 24.7 CPU Temps
«
Reply #78 on:
September 04, 2024, 07:59:30 pm »
For me the following somehow works:
Setting the tunable "dev.hwpstate_intel.*.epp" to 80 seems to avoid too much spiking of the CPU and results in a sane behaviour of the temperature widget.
I missed the fact that for newer CPUs the powerd daemon does not work.
As i don't need very much processing power for my setup there is no need for higher frequencies.
Hardware: J6412 Protectli VP2420
Logged
irrenarzt
Newbie
Posts: 16
Karma: 0
Re: 24.7 CPU Temps
«
Reply #79 on:
October 25, 2024, 06:13:37 pm »
Sorry to bring up an old thread, but this latest 24.7.7 update seems to have helped reduce the CPU utilization problem. I'm still not at pre-24.7 levels, but it's definitely a welcome steep drop I can see in my health reporting charts. Another user in the update thread on Reddit has posted the same positive observation.
Does anyone know what changed that improved this?
Logged
passeri
Full Member
Posts: 100
Karma: 4
Re: 24.7 CPU Temps
«
Reply #80 on:
October 26, 2024, 12:08:56 am »
Holy Heisenberg, Batman.
Sorry, that related to the general problem of measuring temps affecting temps, and I am not sure how to delete it from this context.
Logged
Print
Pages:
1
...
4
5
[
6
]
« previous
next »
OPNsense Forum
»
English Forums
»
24.7 Production Series
»
24.7 CPU Temps