[GH-ISSUE #119] [Question] How snapshot could be used #71

New issue

Closed

opened 2026-05-05 03:24:30 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 03:24:30 -06:00

Owner

Originally created by @Xiang-cd on GitHub (Jan 30, 2024).
Original GitHub issue: https://github.com/XuehaiPan/nvitop/issues/119

Originally assigned to: @XuehaiPan on GitHub.

Required prerequisites

I have read the documentation https://nvitop.readthedocs.io.
I have searched the Issue Tracker that this hasn't already been reported. (comment there if it has.)
I have tried the latest version of nvitop in a new isolated virtual environment.

Questions

thank you for your great work! I've seen the as_snapshot function, but I was wondering how the snapshot could be used?
is the snapshot resumable? because I didn't see the resume interface.

Originally created by @Xiang-cd on GitHub (Jan 30, 2024). Original GitHub issue: https://github.com/XuehaiPan/nvitop/issues/119 Originally assigned to: @XuehaiPan on GitHub. ### Required prerequisites - [X] I have read the documentation <https://nvitop.readthedocs.io>. - [X] I have searched the [Issue Tracker](https://github.com/XuehaiPan/nvitop/issues) that this hasn't already been reported. (comment there if it has.) - [ ] I have tried the latest version of nvitop in a new isolated virtual environment. ### Questions thank you for your great work! I've seen the as_snapshot function, but I was wondering how the snapshot could be used? is the snapshot resumable? because I didn't see the resume interface.

gitea-mirror

2026-05-05 03:24:30 -06:00

closed this issue
added the
api

question
labels

gitea-mirror commented

2026-05-05 03:24:33 -06:00

Author

Owner

@XuehaiPan commented on GitHub (Jan 30, 2024):

@Xiang-cd Thanks for raising this.

The Device / GpuProcess instance is live object to get the latest metrics via method calls. E.g.:

device = Device(0)

device.gpu_utilization()  # -> 96
time.sleep(1)
device.gpu_utilization()  # -> 80  # the latest value from a new NVML API call

Once it is converted to snapshot, the metrics are forzen. The metrcis values are obtained at the time you call as_snapshot().

device = Device(0)

snapshot = device.as_snapshot()
snapshot.gpu_utilization  # -> 94
time.sleep(1)
snapshot.gpu_utilization  # -> 94 (always the freezed value)

You can access the device object via:

snapshot = device.as_snapshot()

snapshot.real  # -> Device(...)

# Get a new snapshot
snapshot = snapshot.real.as_snapshot()
# or
snapshot = device.as_snapshot()

@XuehaiPan commented on GitHub (Jan 30, 2024): @Xiang-cd Thanks for raising this. The `Device` / `GpuProcess` instance is live object to get the latest metrics via method calls. E.g.: ```python device = Device(0) device.gpu_utilization() # -> 96 time.sleep(1) device.gpu_utilization() # -> 80 # the latest value from a new NVML API call ``` Once it is converted to snapshot, the metrics are forzen. The metrcis values are obtained at the time you call `as_snapshot()`. ```python device = Device(0) snapshot = device.as_snapshot() snapshot.gpu_utilization # -> 94 time.sleep(1) snapshot.gpu_utilization # -> 94 (always the freezed value) ``` You can access the device object via: ```python snapshot = device.as_snapshot() snapshot.real # -> Device(...) # Get a new snapshot snapshot = snapshot.real.as_snapshot() # or snapshot = device.as_snapshot() ```

gitea-mirror commented

2026-05-05 03:24:34 -06:00

Author

Owner

@Xiang-cd commented on GitHub (Feb 11, 2024):

thank you, so the snapshot is not a context containing all memory content and register status that could move all context of one device to another device?

@Xiang-cd commented on GitHub (Feb 11, 2024): thank you, so the snapshot is not a context containing all memory content and register status that could move all context of one device to another device?