-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE SUGGESTION] CPU Governor #8
Comments
Thanks for your suggestion again. I dont know much about governors, but I'm not much into playing with them on an hypervisor appart if this is part of any official recommandations, documentations, or documented and proved to be reliable without any side effects at all. What consumption reduction did you experienced? is it really worth-it? Do you have any proof of work link or tests? |
Hi @Tontonjo, I originally dug into this when I was first using Proxmox, so I was going off my own documentation. However, I have re-dug and got some results for you. My system:
With CPU governor set at
With CPU governor set at
Also, Resourceshttps://wiki.archlinux.org/title/CPU_frequency_scaling#cpupower |
Thanks for this - looks interesting for home setups! EDIT: just tested on my system - looking promising: |
Hello! After some testings on some systems, this does not looks to ba a game changer but it may be interesting for some people - Will add this in my Proxmox commands.md. |
Thanks for looking into :) |
For others who come across this, check out this script. https://github.com/tteck/Proxmox/raw/main/misc/scaling-governor.sh |
Hello! I also updated the Proxmox commands guide here with thoses new informations: PS: It does not looks like this script can make sure the selected CPU gouvernor is applied after a reboot. is it? |
Hi, I recently setup a second node and came across a few things that might be useful to add to the Toolbox
Third up, is CPU governor.
I generally change this to
ondemand
on a new install which reduces power consumption but doesn't seem to affect performance.I do this with the below command:
Then add a cron job to run at each boot:
The text was updated successfully, but these errors were encountered: