OPNsense Forum

English Forums => 25.1, 25.4 Production Series => Topic started by: Gary7 on February 20, 2025, 02:47:42 AM

Title: Minor(?) detail with OPNsense 25.1.1 and setting " vm.numa.disabled"
Post by: Gary7 on February 20, 2025, 02:47:42 AM
OPNsense 24.7.5
This update also disables NUMA by default which can bring a boost in network throughput on affected systems. 
system: default to vm.numa.disabled=1


OPNsense 25.1.1
execute: sysctl vm.numa.disabled and the value is vm.numa.disabled: 0
I've added "vm.numa.disabled" to Tunables and verified that vm.numa.disabled="1" is in /boot/loader.conf
After reboot, the value is still vm.numa.disabled: 0

Since I have an APU2D4, I would like to explicitly disable NUMA.
Am I missing something?

Title: Re: Minor(?) detail with OPNsense 25.1.1 and setting " vm.numa.disabled"
Post by: Patrick M. Hausen on February 20, 2025, 07:43:25 AM
An APU2D4 does not have NUMA, so there's nothing to disable.
Title: Re: Minor(?) detail with OPNsense 25.1.1 and setting " vm.numa.disabled"
Post by: franco on February 20, 2025, 09:41:21 AM
Setting correct sysctl/tunable policies across all hardware is so hard to pull off without noise like this.

Functionally, it's fine.


Sorry,
Franco
Title: Re: Minor(?) detail with OPNsense 25.1.1 and setting " vm.numa.disabled"
Post by: Gary7 on February 20, 2025, 03:39:15 PM
Thank you for the clarification. I didn't know if the setting had any effect on a non-NUMA CPU.
I apologize for the noise.
Title: Re: Minor(?) detail with OPNsense 25.1.1 and setting " vm.numa.disabled"
Post by: franco on February 21, 2025, 03:35:56 PM
No worries, these reports are very much appreciated. When numa isn't attached the sysctl isn't attached either so it simply complains about that.


Cheers,
Franco