Last active
January 12, 2025 21:08
-
-
Save DavidMetcalfe/fabbd2ddcb6ba4927269f6f0db31a92f to your computer and use it in GitHub Desktop.
Documents the PowerMizer CLI for potential cron jobs, etc.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Because PowerMizer settings in NVIDIA X Server Settings doesn't persist across sessions, | |
attempts to overclock can become a nuisance. | |
The following documents the three CLI settings to modify the Preferred Mode as desired: | |
# Auto: | |
nvidia-settings -a [gpu:0]/GPUPowerMizerMode=2 | |
# Adaptive: | |
nvidia-settings -a [gpu:0]/GPUPowerMizerMode=0 | |
# Prefer Maximum Performance: | |
nvidia-settings -a [gpu:0]/GPUPowerMizerMode=1 | |
To get rid of the output from these commands, pipe it into /dev/null like so: | |
nvidia-settings -a [gpu:0]/GPUPowerMizerMode=1 > /dev/null | |
# Confirmation: | |
The NVIDIA X Server Settings GUI will toggle to the chosen Preferred Mode, but if wanting to confirm on the CLI, the following will work: | |
nvidia-settings -q [gpu:0]/GPUPowerMizerMode | |
Typical output looks like this: | |
Attribute 'GPUPowerMizerMode' (ComputerName:0[gpu:0]): 1. | |
Valid values for 'GPUPowerMizerMode' are: 0, 1 and 2. | |
'GPUPowerMizerMode' can use the following target types: GPU. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment