nvidia−smi(1) NVIDIA nvidia−smi(1)

NAME
nvidia−smi − NVIDIA System Management Interface program

SYNOPSIS
nvidia-smi [OPTION1 [ARG1]] [OPTION2 [ARG2]] ...

DESCRIPTION
nvidia-smi (also NVSMI) provides monitoring and management capabilities for each of NVIDIA's Tesla,
Quadro, GRID and GeForce devices from Fermi and higher architecture families. GeForce Titan series
devices are supported for most functions with very limited information provided for the remainder of the
Geforce brand. NVSMI is a cross platform tool that supports all standard NVIDIA driver-supported Linux
distros, as well as 64bit versions of Windows starting with Windows Server 2008 R2. Metrics can be con-
sumed directly by users via stdout, or provided by file via CSV and XML formats for scripting purposes.
Note that much of the functionality of NVSMI is provided by the underlying NVML C-based library. See
the NVIDIA developer website link below for more information about NVML. NVML-based python bind-
ings are also available.
The output of NVSMI is not guaranteed to be backwards compatible. However, both NVML and the
Python bindings are backwards compatible, and should be the first choice when writing any tools that must
be maintained across NVIDIA driver releases.
NVML SDK: http://developer.nvidia.com/nvidia-management-library-nvml/
Python bindings: http://pypi.python.org/pypi/nvidia-ml-py/

OPTIONS
GENERAL OPTIONS
−h, −−help
Print usage information and exit.

SUMMARY OPTIONS
−L, −−list−gpus
List each of the NVIDIA GPUs in the system, along with their UUIDs.

QUERY OPTIONS
−q, −−query
Display GPU or Unit info. Displayed info includes all data listed in the (GPU ATTRIBUTES) or (UNIT
ATTRIBUTES) sections of this document. Some devices and/or environments don't support all possible
information. Any unsupported data is indicated by a "N/A" in the output. By default information for all
available GPUs or Units is displayed. Use the −i option to restrict the output to a single GPU or Unit.

[plus optional]
−u, −−unit
Display Unit data instead of GPU data. Unit data is only available for NVIDIA S−class Tesla enclosures.

−i, −−id=ID
Display data for a single specified GPU or Unit. The specified id may be the GPU/Unit's 0−based index in
the natural enumeration returned by the driver, the GPU's board serial number, the GPU's UUID, or the
GPU's PCI bus ID (as domain:bus:device.function in hex). It is recommended that users desiring consis-
tency use either UUID or PCI bus ID, since device enumeration ordering is not guaranteed to be consistent
between reboots and board serial number might be shared between multiple GPUs on the same board.

nvidia−smi 387.12 2017/10/3 1

nvidia−smi(1) NVIDIA nvidia−smi(1)

−f FILE, −−filename=FILE
Redirect query output to the specified file in place of the default stdout. The specified file will be overwrit-
ten.

−x, −−xml−format
Produce XML output in place of the default human−readable format. Both GPU and Unit query outputs
conform to corresponding DTDs. These are available via the −−dtd flag.

−−dtd
Use with −x. Embed the DTD in the XML output.

−−debug=FILE
Produces an encrypted debug log for use in submission of bugs back to NVIDIA.

−d TYPE, −−display=TYPE
Display only selected information: MEMORY, UTILIZATION, ECC, TEMPERATURE, POWER,
CLOCK, COMPUTE, PIDS, PERFORMANCE, SUPPORTED_CLOCKS, PAGE_RETIREMENT,
ACCOUNTING Flags can be combined with comma e.g. "MEMORY,ECC". Sampling data with max,
min and avg is also returned for POWER, UTILIZATION and CLOCK display types. Doesn't work with
-u/--unit or -x/--xml-format flags.

−l SEC, −−loop=SEC
Continuously report query data at the specified interval, rather than the default of just once. The applica-
tion will sleep in−between queries. Note that on Linux ECC error or XID error events will print out during
the sleep period if the -x flag was not specified. Pressing Ctrl+C at any time will abort the loop, which will
otherwise run indefinitely. If no argument is specified for the −l form a default interval of 5 seconds is
used.

SELECTIVE QUERY OPTIONS

Allows the caller to pass an explicit list of properties to query.

[one of]
−−query−gpu=
Information about GPU. Pass comma separated list of properties you want to query. e.g.
−−query−gpu=pci.bus_id,persistence_mode. Call −−help−query−gpu for more info.

−−query−supported−clocks=
List of supported clocks. Call −−help−query−supported−clocks for more info.

−−query−compute−apps=
List of currently active compute processes. Call −−help−query−compute−apps for more info.
−−query−accounted−apps=
List of accounted compute processes. Call −−help−query−accounted−apps for more info.

−−query−retired−pages=
List of GPU device memory pages that have been retired. Call −−help−query−retired−pages for more info.

nvidia−smi 387.12 2017/10/3 2

nvidia−smi(1) NVIDIA nvidia−smi(1)

[mandatory]
−−format=
Comma separated list of format options:
• csv - comma separated values (MANDATORY)
• noheader - skip first line with column headers
• nounits - don’t print units for numerical values

[plus any of]

−i, −−id=ID
Display data for a single specified GPU. The specified id may be the GPU's 0−based index in the natural
enumeration returned by the driver, the GPU's board serial number, the GPU's UUID, or the GPU's PCI bus
ID (as domain:bus:device.function in hex). It is recommended that users desiring consistency use either
UUID or PCI bus ID, since device enumeration ordering is not guaranteed to be consistent between reboots
and board serial number might be shared between multiple GPUs on the same board.

−f FILE, −−filename=FILE
Redirect query output to the specified file in place of the default stdout. The specified file will be overwrit-
ten.

−l SEC, −−loop=SEC
Continuously report query data at the specified interval, rather than the default of just once. The applica-
tion will sleep in−between queries. Note that on Linux ECC error or XID error events will print out during
the sleep period if the -x flag was not specified. Pressing Ctrl+C at any time will abort the loop, which will
otherwise run indefinitely. If no argument is specified for the −l form a default interval of 5 seconds is
used.

−lms ms, −−loop−ms=ms

Same as −l,−−loop but in milliseconds.

DEVICE MODIFICATION OPTIONS

[any one of]
−pm, −−persistence−mode=MODE
Set the persistence mode for the target GPUs. See the (GPU ATTRIBUTES) section for a description of
persistence mode. Requires root. Will impact all GPUs unless a single GPU is specified using the −i argu-
ment. The effect of this operation is immediate. However, it does not persist across reboots. After each
reboot persistence mode will default to "Disabled". Available on Linux only.

−e, −−ecc−config=CONFIG
Set the ECC mode for the target GPUs. See the (GPU ATTRIBUTES) section for a description of ECC
mode. Requires root. Will impact all GPUs unless a single GPU is specified using the −i argument. This
setting takes effect after the next reboot and is persistent.

−p, −−reset−ecc−errors=TYPE
Reset the ECC error counters for the target GPUs. See the (GPU ATTRIBUTES) section for a description
of ECC error counter types. Available arguments are 0|VOLATILE or 1|AGGREGATE. Requires root.
Will impact all GPUs unless a single GPU is specified using the −i argument. The effect of this operation
is immediate.

nvidia−smi 387.12 2017/10/3 3

nvidia−smi(1) NVIDIA nvidia−smi(1)

−c, −−compute−mode=MODE
Set the compute mode for the target GPUs. See the (GPU ATTRIBUTES) section for a description of com-
pute mode. Requires root. Will impact all GPUs unless a single GPU is specified using the −i argument.
The effect of this operation is immediate. However, it does not persist across reboots. After each reboot
compute mode will reset to "DEFAULT".

−dm TYPE, −−driver−model=TYPE

−fdm TYPE, −−force−driver−model=TYPE
Enable or disable TCC driver model. For Windows only. Requires administrator privileges. −dm will fail
if a display is attached, but −fdm will force the driver model to change. Will impact all GPUs unless a sin-
gle GPU is specified using the −i argument. A reboot is required for the change to take place. See Driver
Model for more information on Windows driver models.

−−gom=MODE
Set GPU Operation Mode: 0/ALL_ON, 1/COMPUTE, 2/LOW_DP Supported on GK110 M-class and X-
class Tesla products from the Kepler family. Not supported on Quadro and Tesla C-class products.
LOW_DP and ALL_ON are the only modes supported on GeForce Titan devices. Requires administrator
privileges. See GPU Operation Mode for more information about GOM. GOM changes take effect after
reboot. The reboot requirement might be removed in the future. Compute only GOMs don’t support
WDDM (Windows Display Driver Model)

−r, −−gpu−reset
Trigger a reset of one or more GPUs. Can be used to clear GPU HW and SW state in situations that would
otherwise require a machine reboot. Typically useful if a double bit ECC error has occurred. Optional −i
switch can be used to target one or more specific devices. Without this option, all GPUs are reset.
Requires root. There can't be any applications using these devices (e.g. CUDA application, graphics appli-
cation like X server, monitoring application like other instance of nvidia-smi). There also can't be any com-
pute applications running on any other GPU in the system.

When resetting GPUs that have active NVLink connections to other GPUs, all GPUs with active NVLink
connections must be reset together, either by omitting the −i switch or using the −i switch to specify all
GPUs with active NVLink connections.

GPU reset is not guaranteed to work in all cases. It is not recommended for production environments at this
time. In some situations there may be HW components on the board that fail to revert back to an initial
state following the reset request. This is more likely to be seen on Fermi-generation products vs. Kepler,
and more likely to be seen if the reset is being performed on a hung GPU.

Following a reset, it is recommended that the health of each reset GPU be verified before further use. The
nvidia-healthmon tool is a good choice for this test. If any GPU is not healthy a complete reset should be
instigated by power cycling the node.

Visit http://developer.nvidia.com/gpu-deployment-kit to download the GDK and nvidia-healthmon.

−ac, −−applications−clocks=MEM_CLOCK,GRAPHICS_CLOCK
Specifies maximum <memory,graphics> clocks as a pair (e.g. 2000,800) that defines GPU’s speed while
running applications on a GPU. Supported on Maxwell-based GeForce and from the Kepler+ family in
Tesla/Quadro/Titan devices. Requires root unless restrictions are relaxed with the −acp command..

−rac, −−reset−applications−clocks
Resets the applications clocks to the default value. Supported on Maxwell-based GeForce and from the
Kepler+ family in Tesla/Quadro/Titan devices. Requires root unless restrictions are relaxed with the −acp

nvidia−smi 387.12 2017/10/3 4

nvidia−smi(1) NVIDIA nvidia−smi(1)

command.

−acp, −−applications−clocks−permission=MODE
Toggle whether applications clocks can be changed by all users or only by root. Available arguments are
0|UNRESTRICTED, 1|RESTRICTED. Supported on Maxwell-based GeForce and from the Kepler+ fam-
ily in Tesla/Quadro/Titan devices. Requires root.

−pl, −−power−limit=POWER_LIMIT
Specifies maximum power limit in watts. Accepts integer and floating point numbers. Only on supported
devices from Kepler family. Requires administrator privileges. Value needs to be between Min and Max
Power Limit as reported by nvidia-smi.

−am, −−accounting−mode=MODE
Enables or disables GPU Accounting. With GPU Accounting one can keep track of usage of resources
throughout lifespan of a single process. Only on supported devices from Kepler family. Requires adminis-
trator privileges. Available arguments are 0|DISABLED or 1|ENABLED.

−caa, −−clear−accounted−apps
Clears all processes accounted so far. Only on supported devices from Kepler family. Requires administra-
tor privileges.

−−auto−boost−default=MODE
Set the default auto boost policy to 0/DISABLED or 1/ENABLED, enforcing the change only after the last
boost client has exited. Only on certain Tesla devices from the Kepler+ family and Maxwell-based
GeForce devices. Requires root.

−−auto−boost−default−force=MODE
Set the default auto boost policy to 0/DISABLED or 1/ENABLED, enforcing the change immediately.
Only on certain Tesla devices from the Kepler+ family and Maxwell-based GeForce devices. Requires
root.

−−auto−boost−permission=MODE
Allow non-admin/root control over auto boost mode. Available arguments are 0|UNRESTRICTED,
1|RESTRICTED. Only on certain Tesla devices from the Kepler+ family and Maxwell-based GeForce
devices. Requires root.

[plus optional]
−i, −−id=ID
Modify a single specified GPU. The specified id may be the GPU/Unit's 0−based index in the natural enu-
meration returned by the driver, the GPU's board serial number, the GPU's UUID, or the GPU's PCI bus ID
(as domain:bus:device.function in hex). It is recommended that users desiring consistency use either UUID
or PCI bus ID, since device enumeration ordering is not guaranteed to be consistent between reboots and
board serial number might be shared between multiple GPUs on the same board.

UNIT MODIFICATION OPTIONS

−t, −−toggle−led=STATE
Set the LED indicator state on the front and back of the unit to the specified color. See the (UNIT
ATTRIBUTES) section for a description of the LED states. Allowed colors are 0|GREEN and 1|AMBER.
Requires root.

nvidia−smi 387.12 2017/10/3 5

nvidia−smi(1) NVIDIA nvidia−smi(1)

[plus optional]
−i, −−id=ID
Modify a single specified Unit. The specified id is the Unit's 0-based index in the natural enumeration
returned by the driver.

SHOW DTD OPTIONS

−−dtd
Display Device or Unit DTD.

[plus optional]
−f FILE, −−filename=FILE
Redirect query output to the specified file in place of the default stdout. The specified file will be overwrit-
ten.

−u, −−unit
Display Unit DTD instead of device DTD.

stats
Display statistics information about the GPU. Use "nvidia-smi stats -h" for more information. Linux only.

topo
Display topology information about the system. Use "nvidia-smi topo -h" for more information. Linux
only. Shows all GPUs NVML is able to detect but CPU affinity information will only be shown for GPUs
with Kepler or newer architectures. Note: GPU enumeration is the same as NVML.

drain
Display and modify the GPU drain states. Use "nvidia-smi drain -h" for more information. Linux only.

nvlink
Display nvlink information. Use "nvidia-smi nvlink -h" for more information.

clocks
Query and control clocking behavior. Currently, this only pertains to synchronized boost. Use "nvidia-smi
clocks --help" for more information.

vgpu
Display information on GRID virtual GPUs. Use "nvidia-smi vgpu -h" for more information.

RETURN VALUE
Return code reflects whether the operation succeeded or failed and what was the reason of failure.
• Return code 0 − Success
• Return code 2 − A supplied argument or flag is invalid
• Return code 3 − The requested operation is not available on target device
• Return code 4 − The current user does not have permission to access this device or perform this
operation
• Return code 6 − A query to find an object was unsuccessful

nvidia−smi 387.12 2017/10/3 6

nvidia−smi(1) NVIDIA nvidia−smi(1)
nvidia−smi(1) NVIDIA nvidia−smi(1)

Please note that power readings are not applicable for Pascal and higher GPUs with BA sensor boards.

Power State Power State is deprecated and has been renamed to Performance State in 2.285. To
maintain XML compatibility, in XML format Performance State is listed in both places.

Power Management
A flag that indicates whether power management is enabled. Either "Supported" or
"N/A". Requires Inforom PWR object version 3.0 or higher or Kepler device.

Power Draw The last measured power draw for the entire board, in watts. Only available if power
management is supported. This reading is accurate to within +/- 5 watts. Requires
Inforom PWR object version 3.0 or higher or Kepler device. Please note that for boards
without INA sensors, this refers to the power draw for the GPU and not for the entire
board.

Power Limit The software power limit, in watts. Set by software such as nvidia-smi. Only available
if power management is supported. Requires Inforom PWR object version 3.0 or higher
or Kepler device. On Kepler devices Power Limit can be adjusted using
−pl,−−power−limit= switches.

Enforced Power Limit

The power management algorithm's power ceiling, in watts. Total board power draw is
manipulated by the power management algorithm such that it stays under this value.
This limit is the minimum of various limits such as the software limit listed above. Only
available if power management is supported. Requires a Kepler device. Please note that
for boards without INA sensors, it is the GPU power draw that is being manipulated.

Default Power Limit

The default power management algorithm's power ceiling, in watts. Power Limit will be
set back to Default Power Limit after driver unload. Only on supported devices from
Kepler family.

Min Power Limit

The minimum value in watts that power limit can be set to. Only on supported devices
from Kepler family.

Max Power Limit

The maximum value in watts that power limit can be set to. Only on supported devices
from Kepler family.

Clocks
Current frequency at which parts of the GPU are running. All readings are in MHz.

Graphics Current frequency of graphics (shader) clock.

SM Current frequency of SM (Streaming Multiprocessor) clock.

Memory Current frequency of memory clock.

nvidia−smi 387.12 2017/10/3 14

nvidia−smi(1) NVIDIA nvidia−smi(1)

Video Current frequency of video (encoder + decoder) clocks.

Applications Clocks
User specified frequency at which applications will be running at. Can be changed with [−ac | −−applica-
tions−clocks] switches.

Graphics User specified frequency of graphics (shader) clock.

Memory User specified frequency of memory clock.

Default Applications Clocks

Default frequency at which applications will be running at. Application clocks can be changed with [−ac |
−−applications−clocks] switches. Application clocks can be set to default using [−rac | −−reset−applica-
tions−clocks] switches.

Graphics Default frequency of applications graphics (shader) clock.

Memory Default frequency of applications memory clock.

Max Clocks
Maximum frequency at which parts of the GPU are design to run. All readings are in MHz.

On GPUs from Fermi family current P0 clocks (reported in Clocks section) can differ from max clocks by
few MHz.

Graphics Maximum frequency of graphics (shader) clock.

SM Maximum frequency of SM (Streaming Multiprocessor) clock.

Memory Maximum frequency of memory clock.

Video Maximum frequency of video (encoder + decoder) clock.

Clock Policy
User-specified settings for automated clocking changes such as auto boost.

Auto Boost Indicates whether auto boost mode is currently enabled for this GPU (On) or disabled for
this GPU (Off). Shows (N/A) if boost is not supported. Auto boost allows dynamic GPU
clocking based on power, thermal and utilization. When auto boost is disabled the GPU
will attempt to maintain clocks at precisely the Current Application Clocks settings
(whenever a CUDA context is active). With auto boost enabled the GPU will still attempt
to maintain this floor, but will opportunistically boost to higher clocks when power, ther-
mal and utilization headroom allow. This setting persists for the life of the CUDA con-
text for which it was requested. Apps can request a particular mode either via an NVML
call (see NVML SDK) or by setting the CUDA environment variable
CUDA_AUTO_BOOST.

nvidia−smi 387.12 2017/10/3 15

nvidia−smi(1) NVIDIA nvidia−smi(1)

Auto Boost Default

Indicates the default setting for auto boost mode, either enabled (On) or disabled (Off).
Shows (N/A) if boost is not supported. Apps will run in the default mode if they have not
explicitly requested a particular mode. Note: Auto Boost settings can only be modified if
"Persistence Mode" is enabled, which is NOT by default.

Supported clocks
List of possible memory and graphics clocks combinations that the GPU can operate on (not taking into
account HW brake reduced clocks). These are the only clock combinations that can be passed to −−appli-
cations−clocks flag. Supported Clocks are listed only when −q −d SUPPORTED_CLOCKS switches are
provided or in XML format.

Processes
List of processes having Compute or Graphics Context on the device. Compute processes are reported on
all the fully supported products. Reporting for Graphics processes is limited to the supported products start-
ing with Kepler architecture.

Each Entry is of format "<GPU Index> <PID> <Type> <Process Name> <GPU Memory Usage>"

GPU Index Represents NVML Index of the device.

PID Represents Process ID corresponding to the active Compute or Graphics context.

Type Displayed as "C" for Compute Process, "G" for Graphics Process, and "C+G" for the
process having both Compute and Graphics contexts.

Process Name Represents process name for the Compute or Graphics process.

GPU Memory Usage

Amount of memory used on the device by the context. Not available on Windows when
running in WDDM mode because Windows KMD manages all the memory not NVIDIA
driver.

Stats (EXPERIMENTAL)
List GPU statistics such as power samples, utilization samples, xid events, clock change events and viola-
tion counters.
Supported on Tesla, GRID and Quadro based products under Linux.
Limited to Kepler or newer GPUs.

Displays statistics in CSV format as follows:

<GPU device index>, <metric name>, <CPU Timestamp in us>, <value for metric>

The metrics to display with their units are as follows:

Power samples in Watts.
GPU Temperature samples in degrees Celsius.

nvidia−smi 387.12 2017/10/3 16

nvidia−smi(1) NVIDIA nvidia−smi(1)

GPU, Memory, Encoder and Decoder utilization samples in Percentage.

Xid error events reported with Xid error code. The error code is 999 for unknown xid error.
Processor and Memory clock changes in MHz.
Violation due to Power capping with violation time in ns. (Tesla Only)
Violation due to Thermal capping with violation boolean flag (1/0). (Tesla Only)

Notes:
Any statistic preceded by "#" is a comment.
Non supported device is displayed as "#<device Index>, Device not supported".
Non supported metric is displayed as "<device index>, <metric name>, N/A, N/A".
Violation due to Thermal/Power supported only for Tesla based products. Thermal Violations are limited to
Tesla K20 and higher.

Device Monitoring
The "nvidia-smi dmon" command-line is used to monitor one or more GPUs (up to 4 devices) plugged into
the system. This tool allows the user to see one line of monitoring data per monitoring cycle. The output is
in concise format and easy to interpret in interactive mode. The output data per line is limited by the termi-
nal size. It is supported on Tesla, GRID, Quadro and limited GeForce products for Kepler or newer GPUs
under bare metal 64 bits Linux. By default, the monitoring data includes Power Usage, Temperature, SM
clocks, Memory clocks and Utilization values for SM, Memory, Encoder and Decoder. It can also be con-
figured to report other metrics such as frame buffer memory usage, bar1 memory usage, power/thermal vio-
lations and aggregate single/double bit ecc errors. If any of the metric is not supported on the device or any
other error in fetching the metric is reported as "-" in the output data. The user can also configure monitor-
ing frequency and the number of monitoring iterations for each run. There is also an option to include date
and time at each line. All the supported options are exclusive and can be used together in any order.

Usage:
1) Default with no arguments
nvidia-smi dmon
Monitors default metrics for up to 4 supported devices under natural enumeration (starting with GPU index
0) at a frequency of 1 sec. Runs until terminated with ˆC.

2) Select one or more devices

nvidia-smi dmon -i <device1,device2, .. , deviceN>
Reports default metrics for the devices selected by comma separated device list. The tool picks up to 4 sup-
ported devices from the list under natural enumeration (starting with GPU index 0).

3) Select metrics to be displayed

nvidia-smi dmon -s <metric_group>
<metric_group> can be one or more from the following:
p - Power Usage (in Watts) and Temperature (in C)
u - Utilization (SM, Memory, Encoder and Decoder Utilization in %)
c - Proc and Mem Clocks (in MHz)

nvidia−smi 387.12 2017/10/3 17

nvidia−smi(1) NVIDIA nvidia−smi(1)

v - Power Violations (in %) and Thermal Violations (as a boolean flag)

m - Frame Buffer and Bar1 memory usage (in MB)
e - ECC (Number of aggregated single bit, double bit ecc errors) and PCIe Replay errors
t - PCIe Rx and Tx Throughput in MB/s (Maxwell and above)

4) Configure monitoring iterations

nvidia-smi dmon -c <number of samples>
Displays data for specified number of samples and exit.

5) Configure monitoring frequency

nvidia-smi dmon -d <time in secs>
Collects and displays data at every specified monitoring interval until terminated with ˆC.

6) Display date
nvidia-smi dmon -o D
Prepends monitoring data with date in YYYYMMDD format.

7) Display time
nvidia-smi dmon -o T
Prepends monitoring data with time in HH:MM:SS format.

8) Help Information
nvidia-smi dmon -h
Displays help information for using the command line.

Daemon (EXPERIMENTAL)
The "nvidia-smi daemon" starts a background process to monitor one or more GPUs plugged in to the sys-
tem. It monitors the requested GPUs every monitoring cycle and logs the file in compressed format at the
user provided path or the default location at /var/log/nvstats/. The log file is created with system’s date
appended to it and of the format nvstats-YYYYMMDD. The flush operation to the log file is done every
alternate monitoring cycle. Daemon also logs it’s own PID at /var/run/nvsmi.pid. By default, the monitoring
data to persist includes Power Usage, Temperature, SM clocks, Memory clocks and Utilization values for
SM, Memory, Encoder and Decoder. The daemon tools can also be configured to record other metrics such
as frame buffer memory usage, bar1 memory usage, power/thermal violations and aggregate single/double
bit ecc errors.The default monitoring cycle is set to 10 secs and can be configured via command-line. It is
supported on Tesla, GRID, Quadro and GeForce products for Kepler or newer GPUs under bare metal 64
bits Linux. The daemon requires root privileges to run, and only supports running a single instance on the
system. All of the supported options are exclusive and can be used together in any order.

Usage:
1) Default with no arguments
nvidia-smi daemon
Runs in the background to monitor default metrics for up to 4 supported devices under natural enumeration
(starting with GPU index 0) at a frequency of 10 sec. The date stamped log file is created at /var/log/nvs-
tats/.

nvidia−smi 387.12 2017/10/3 18

nvidia−smi(1) NVIDIA nvidia−smi(1)

2) Select one or more devices

nvidia-smi daemon -i <device1,device2, .. , deviceN>
Runs in the background to monitor default metrics for the devices selected by comma separated device list.
The tool picks up to 4 supported devices from the list under natural enumeration (starting with GPU index
0).

3) Select metrics to be monitored

nvidia-smi daemon -s <metric_group>
<metric_group> can be one or more from the following:
p - Power Usage (in Watts) and Temperature (in C)
u - Utilization (SM, Memory, Encoder and Decoder Utilization in %)
c - Proc and Mem Clocks (in MHz)
v - Power Violations (in %) and Thermal Violations (as a boolean flag)
m - Frame Buffer and Bar1 memory usage (in MB)
e - ECC (Number of aggregated single bit, double bit ecc errors) and PCIe Replay errors
t - PCIe Rx and Tx Throughput in MB/s (Maxwell and above)

4) Configure monitoring frequency

nvidia-smi daemon -d <time in secs>
Collects data at every specified monitoring interval until terminated.

5) Configure log directory

nvidia-smi daemon -p <path of directory>
The log files are created at the specified directory.

6) Configure log file name

nvidia-smi daemon -j <string to append log file name>
The command-line is used to append the log file name with the user provided string.

7) Terminate the daemon

nvidia-smi daemon -t
This command-line uses the stored PID (at /var/run/nvsmi.pid) to terminate the daemon. It makes the best
effort to stop the daemon and offers no guarantees for it’s termination. In case the daemon is not termi-
nated, then the user can manually terminate by sending kill signal to the daemon. Performing a GPU reset
operation (via nvidia-smi) requires all GPU processes to be exited, including the daemon. Users who have
the daemon open will see an error to the effect that the GPU is busy.

8) Help Information
nvidia-smi daemon -h
Displays help information for using the command line.

nvidia−smi 387.12 2017/10/3 19

nvidia−smi(1) NVIDIA nvidia−smi(1)

Replay Mode (EXPERIMENTAL)

The "nvidia-smi replay" command-line is used to extract/replay all or parts of log file generated by the dae-
mon. By default, the tool tries to pull the metrics such as Power Usage, Temperature, SM clocks, Memory
clocks and Utilization values for SM, Memory, Encoder and Decoder. The replay tool can also fetch other
metrics such as frame buffer memory usage, bar1 memory usage, power/thermal violations and aggregate
single/double bit ecc errors. There is an option to select a set of metrics to replay, If any of the requested
metric is not maintained or logged as not-supported then it’s shown as "-" in the output. The format of data
produced by this mode is such that the user is running the device monitoring utility interactively. The com-
mand line requires mandatory option "-f" to specify complete path of the log filename, all the other sup-
ported options are exclusive and can be used together in any order.

Usage:
1) Specify log file to be replayed
nvidia-smi replay -f <log file name>
Fetches monitoring data from the compressed log file and allows the user to see one line of monitoring data
(default metrics with time-stamp) for each monitoring iteration stored in the log file. A new line of monitor-
ing data is replayed every other second irrespective of the actual monitoring frequency maintained at the
time of collection. It is displayed till the end of file or until terminated by ˆC.

2) Filter metrics to be replayed

nvidia-smi replay -f <path to log file> -s <metric_group>
<metric_group> can be one or more from the following:
p - Power Usage (in Watts) and Temperature (in C)
u - Utilization (SM, Memory, Encoder and Decoder Utilization in %)
c - Proc and Mem Clocks (in MHz)
v - Power Violations (in %) and Thermal Violations (as a boolean flag)
m - Frame Buffer and Bar1 memory usage (in MB)
e - ECC (Number of aggregated single bit, double bit ecc errors) and PCIe Replay errors
t - PCIe Rx and Tx Throughput in MB/s (Maxwell and above)

3) Limit replay to one or more devices

nvidia-smi replay -f <log file> -i <device1,device2, .. , deviceN>
Limits reporting of the metrics to the set of devices selected by comma separated device list. The tool skips
any of the devices not maintained in the log file.

4) Restrict the time frame between which data is reported

nvidia-smi replay -f <log file> -b <start time in HH:MM:SS format> -e <end time in HH:MM:SS format>
This option allows the data to be limited between the specified time range. Specifying time as 0 with -b or
-e option implies start or end file respectively.

5) Redirect replay information to a log file

nvidia-smi replay -f <log file> -r <output file name>
This option takes log file as an input and extracts the information related to default metrics in the specified
output file.

nvidia−smi 387.12 2017/10/3 20

nvidia−smi(1) NVIDIA nvidia−smi(1)

6) Help Information
nvidia-smi replay -h
Displays help information for using the command line.

Process Monitoring
The "nvidia-smi pmon" command-line is used to monitor compute and graphics processes running on one
or more GPUs (up to 4 de