This has been solved - this thread is for anybody else who has the same problem and is searching for keywords.
An upgrade to Proxmox 7.0 has tanked the performance of virtualized pfSense 2.5.2. Pre-upgrade a download of 100Mbps used about 20% VCPU and now can't reach that bandwidth even 50Mbps needs 100% VCPU. The pfSense GUI and even the command line runs sluggish. Using "systat -vmstat 1" from the pfsense console shows interrupts are dominating the CPU usage (e.g. 70% Intr and 0% Idle).
Finally realized the problem is the default governor on Proxmox 7.0. It was previously "performance" and now runs a power-saving scheduler instead. This has been reported elsewhere in the forums but not in the context of pfSense running slowly due to high CPU usage or interrupts. The solution as posted elsewhere worked immediately and restored normal behaviour to pfSense.
I made this permanent by installing cpufrequtils and creating /etc/default/cpufrequtils
An upgrade to Proxmox 7.0 has tanked the performance of virtualized pfSense 2.5.2. Pre-upgrade a download of 100Mbps used about 20% VCPU and now can't reach that bandwidth even 50Mbps needs 100% VCPU. The pfSense GUI and even the command line runs sluggish. Using "systat -vmstat 1" from the pfsense console shows interrupts are dominating the CPU usage (e.g. 70% Intr and 0% Idle).
Finally realized the problem is the default governor on Proxmox 7.0. It was previously "performance" and now runs a power-saving scheduler instead. This has been reported elsewhere in the forums but not in the context of pfSense running slowly due to high CPU usage or interrupts. The solution as posted elsewhere worked immediately and restored normal behaviour to pfSense.
Code:
echo "performance" | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governorI made this permanent by installing cpufrequtils and creating /etc/default/cpufrequtils
Code:
GOVERNOR=performance
Last edited:
