You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I reviewed the code for the dcgmi tool and found that before querying metrics using the dcgmGetLatestValues_v function in the dmon feature, it first calls dcgmWatchFields and dcgmUpdateAllFields to start monitoring and force a refresh.
However, I noticed that it does not call UnwatchFields after the query is completed. When should UnwatchFields be called?
In my use case, I need to periodically query certain metrics. If I call dcgmWatchFields each time before querying, will there be any additional performance or memory overhead? Or, how should I handle this scenario?
I look forward to your reply
The text was updated successfully, but these errors were encountered:
I reviewed the code for the dcgmi tool and found that before querying metrics using the dcgmGetLatestValues_v function in the dmon feature, it first calls dcgmWatchFields and dcgmUpdateAllFields to start monitoring and force a refresh.
However, I noticed that it does not call UnwatchFields after the query is completed. When should UnwatchFields be called?
In my use case, I need to periodically query certain metrics. If I call dcgmWatchFields each time before querying, will there be any additional performance or memory overhead? Or, how should I handle this scenario?
I look forward to your reply
The text was updated successfully, but these errors were encountered: