Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - rickyricky

#1
23.7 Legacy Series / Re: CPU temp reporting
November 24, 2024, 10:48:46 PM
you're querying the same values, but one method parses MUCH less data than the other...


Here is the dev.cpu method...
```
root@router-02:~ # sysctl dev.cpu | wc -l
     273
```

Looking for temp by looking at only needs to export and grep through 273 lines.



Here is the sysctl -a method...
```
root@router-02:~ # sysctl -a | wc -l
   16497
```

The sysctl has to export 16000+ more lines than the one that only looks at cpu values, then has to grep through those 16k values to find the ones that match the grep.

The 2nd command finishes quickly, but it still causes enough additional cpu load to show the temp has been raised by the time temperature is filtered out by the grep command.



#2
I have two Opnsense routers.  The one on Xfinity does not have this issue.  The one on Spectrum does have the issue.

Is there anything I can do to help or provide additional information?

For now, I've done the cardinal sin of disabling IPv6 on the Spectrum as when the IPv6 routing fails, children yell at me.  Best IPv6 routing notification system I could have implemented. =)