Make GPU residue values consistent across meter instances #1618
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.
GPUMeter_updateValues()
used a locally cached "residue time" variable for computing the percentage of the "GPU residue" usage. The "residue" percentages of subsequentGPUMeter
instances could be 0 due to the cached "residue time" off-sync with the time data from theLinuxMachine
instance.Rewrite the logic of the function so that all computed GPU percentage values are cached, and the cache updated only when there's increment on
host->monotonicMs
.