Yes mir, i have add this params to loader.conf.local but still the load goes from 20% to 55%.
I think that this params are more focused for idle CPU functions, but my pfsense is very active, fw, haproxy and snort
And like say nixcz the interrupts inside pfsense now are really visible just...
Our servers are HP DL360 G8 with two E5-2660 v2 and the 64bits FBSD pfsense hangs on startup with default kernel.
Until yesterday I was comfortable with the 3.10, but now with this CPU Load, not so much :mad:
you can see the increase on CPU load on the virtual pfsense under proxmox
I have the same issue with the last 3.3 update and now our pfsense fw is allways with 50% CPU and with the params at the loader.conf.local now is 20% CPU usage.
pfsense 2.1.3-RELEASE (amd64)
we are also using the 3.10 kernel because the Ivy Bridge/Haswell CPU issue,