NVIDIA Jetson Orin - Evaluating Performance

🚧 Documentation is under development

The NVIDIA Jetson Orin guide is currently under active development. Some sections may be incomplete or change without notice.

Questions? Contact RidgeRun or email to support@ridgerun.com.

Contents Pin

As developers, we often need to measure CPU, GPU, and memory usage to budget the applications that need to run in our projects. NVIDIA provides the tegrastats tool to extract these and other important metrics in Jetson platforms. This section provides an overview of the usage of tegrastats.

tegrastats

tegrastats is a tool that reports memory usage, GPU usage, CPU usage, and SOC temperature for Tegra-based devices. Tegrastats comes installed in the sample root filesystem provided in Jetpack, and it's located in the Orin AGX system path /usr/bin, so it can be launched from any location in the filesystem. To launch tegrastats, simply run the binary with privileges:

sudo tegrastats

This command will start printing the system stats each second, an example of the expected output can be found in the next subsection. If you need to customize the tegrastats behavior, the binary provides the following command-line options:

Usage: tegrastats [-option]
Options:
    --help                   : print this help screen
    --interval <millisec>     : sample the information in <milliseconds>
    --cpu_per_socket <numcpu> : display only the top <numcpu> by utilization per socket (default=6)
                               applicable only for socket-based systems
    --logfile  <filename>     : dump the output of tegrastats to <filename>
    --load_cfg <filename>     : load the information from <filename>
    --readall                : collect all stats including performance intensive stats
    --save_cfg <filename>     : save the information to <filename>
    --start                  : run tegrastats as a daemon process in the background
    --stop                   : stop any running instances of tegrastats
    --verbose                : print verbose message

tegrastats Output

The following Jetson AGX Orin samples show four consecutive readings. Table 1 interprets the fields present in these logs using NVIDIA's documentation.^[1] Field availability and formatting depend on the platform and software version.

10-19-2026 16:12:12 RAM 1294/30670MB (lfb 19x4MB) SWAP 0/2048MB (cached 0MB) CPU [2%@729,0%@729,0%@729,0%@729,0%@729,0%@729,0%@729,0%@729,off,off,off,off] GR3D_FREQ 0% cpu@44.531C/44.531C soc2@40.937C/40.937C soc0@41.718C/41.718C tj@44.531C/44.531C soc1@40.843C/40.843C VDD_GPU_SOC 2000mW/2000mW/2000mW VDD_CPU_CV 0mW/0mW/0mW VIN_SYS_5V0 2329mW/2329mW/2329mW
10-19-2026 16:12:13 RAM 1294/30670MB (lfb 19x4MB) SWAP 0/2048MB (cached 0MB) CPU [1%@729,0%@729,0%@729,0%@729,0%@729,0%@729,0%@729,0%@729,off,off,off,off] GR3D_FREQ 0% cpu@44.656C/44.656C soc2@40.937C/40.937C soc0@41.812C/41.812C tj@44.656C/44.656C soc1@40.718C/40.843C VDD_GPU_SOC 1999mW/2000mW/2000mW VDD_CPU_CV 0mW/0mW/0mW VIN_SYS_5V0 2329mW/2329mW/2329mW
10-19-2026 16:12:14 RAM 1294/30670MB (lfb 19x4MB) SWAP 0/2048MB (cached 0MB) CPU [0%@729,0%@729,0%@729,0%@729,0%@729,0%@729,0%@729,0%@729,off,off,off,off] GR3D_FREQ 0% cpu@44.468C/44.656C soc2@40.937C/40.937C soc0@41.687C/41.812C tj@44.468C/44.656C soc1@40.687C/40.843C VDD_GPU_SOC 2000mW/2000mW/2000mW VDD_CPU_CV 0mW/0mW/0mW VIN_SYS_5V0 2228mW/2295mW/2329mW
10-19-2026 16:12:15 RAM 1294/30670MB (lfb 19x4MB) SWAP 0/2048MB (cached 0MB) CPU [0%@729,1%@729,0%@729,0%@729,0%@729,0%@729,0%@729,0%@729,off,off,off,off] GR3D_FREQ 0% cpu@44.718C/44.718C soc2@40.875C/40.937C soc0@41.812C/41.812C tj@44.718C/44.718C soc1@40.531C/40.843C VDD_GPU_SOC 1999mW/2000mW/2000mW VDD_CPU_CV 0mW/0mW/0mW VIN_SYS_5V0 2228mW/2279mW/2329mW

Table 1: tegrastats interpretation
Statistic	Description
`10-19-2026 16:12:12`	Sample timestamp; subsequent readings are one second apart.
`RAM 1294/30670MB (lfb 19x4MB)`	1294 MB used out of 30670 MB available. The allocator reports 19 largest free physical blocks of 4 MB each; this is not total free RAM.
`SWAP 0/2048MB (cached 0MB)`	0 MB used out of 2048 MB of swap; 0 MB cached.
`CPU [2%@729,0%@729,...,off,off,off,off]`	Per-core utilization and frequency in MHz. Initially, the first core is at 2% and 729 MHz. Eight cores are online at 729 MHz; four are off.
`GR3D_FREQ 0%`	GPU activity is 0%. This sample contains no GPU frequency value.
`cpu@44.531C/44.531C`	CPU thermal zone: 44.531 °C current reading; inferred recorded peak 44.531 °C.
`soc2@40.937C/40.937C`	SoC thermal zone 2: 40.937 °C current reading; inferred recorded peak 40.937 °C.
`soc0@41.718C/41.718C`	SoC thermal zone 0: 41.718 °C current reading; inferred recorded peak 41.718 °C.
`tj@44.531C/44.531C`	TJ maximum-junction thermal zone: 44.531 °C current reading; inferred recorded peak 44.531 °C. The zone name and the peak over time are separate concepts.
`soc1@40.843C/40.843C`	SoC thermal zone 1: 40.843 °C current reading; inferred recorded peak 40.843 °C.
`VDD_GPU_SOC 2000mW/2000mW/2000mW`	GPU and SoC rail, including memory-subsystem and multimedia engines: 2000 mW current, 2000 mW average, and inferred peak 2000 mW.
`VDD_CPU_CV 0mW/0mW/0mW`	CPU and computer-vision rail (DLA and PVA): 0 mW current, average, and inferred peak as reported. This does not establish that the active CPUs consume no power.
`VIN_SYS_5V0 2228mW/2279mW/2329mW`	System 5 V rail supplying I/O and including DDR-related power: final sample reports 2228 mW current, 2279 mW average, and inferred peak 2329 mW. This is not a whole-module power reading.

References

↑ NVIDIA Jetson Linux Developer Guide: Tegrastats Utility

❯

[tegrastats-1] NVIDIA Jetson Linux Developer Guide: Tegrastats Utility

[1]

Share This Page

Send Email Using

tegrastats

tegrastats Output

References