client/scheduler: update NVidia detection again #4031
Merged
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.
for new RTX 30x0 range released September 2020
Description of the Change
GFLOPS peak is under-reported by a factor of 2 on the new cards, compared with other reporting tools
Alternate Designs
I've been asked if we could use NvAPI_GPU_GetGpuCoreCount() instead (available since 2014), but rejected as a more complex modification which might break backwards compatibility.
Release Notes
Correct detection of NVidia RTX30x0 range GPUs