Switch to nvidia-smi to reduce CPU load when fetching GPU temperatures #162
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At least on one Intel systems (i7-8700K/delidded/watercooled) the display of the GPU temperature of NVIDIA cards caused perceptible spikes in CPU utilization, frequency and temperature of individual cores.
This was eventually tracked down to
nvidia-settings
being substantially slower and, more importantly, computationally intensive thannvidia-smi
.Switch the implementation of
nvidiaUtil.js
to usenvidia-smi
. In the process, simplify the label parsing and label vs. temperature code becausenvidia-smi
allows us greater control over the output.nvidia-settings
:nvidia-smi
:Possibly-related: #116 ("How to allow for lower minimum values for CPU?")
Related: #161 ("[Feature Request] Add support for NVIDIA PRIME render offload", user mentions that nvidia-smi solves the issue)