Fix tracking for NVIDIA Blackwell GPUs (catching pynvml.NVMLError_NotSupported) #1038
+5
−1
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.
Description
Added error catching for the static GPU memory information. Behavior only changes when the
pynvmlcall is not successful.Related Issue
#1037
Motivation and Context
For the NVIDIA DGX Spark, CodeCarbon trackers currently cannot be correctly initialized. When debugging into that, I noticed that calling
pynvml.nvmlDeviceGetMemoryInfoincodecarbon/core/gpu.pythrows anpynvml.NVMLError_NotSupported, probably due to the shared memore architecture of the NVIDIA Blackwell GPU (internally read as NVIDIA GB10).How Has This Been Tested?
Locally tested tracking functionality after the fix.
Types of changes
What types of changes does your code introduce? Put an
xin all the boxes that apply:Checklist:
Go over all the following points, and put an
xin all the boxes that apply.