Learn / NVIDIA Jetson / Optimise and deploy

Jetson Power Modes, Heat and Field Deployment

ReviewedAdvanced ProAbout 6 min
NANO
In short

Jetson Power Modes, Heat and Field Deployment: the short answer

A Jetson can trade speed for power. Power modes cap the CPU and GPU clocks and the number of active cores.

Level
Advanced
Time
About 6 min
Topic
NVIDIA Jetson
You will learn to

Choose a power mode, keep the Jetson cool and plan power and recovery for a device in the field.

Before this: First Boot on a Jetson Orin Nano, Power Budgets and Thermal Design

A Jetson can trade speed for power. Power modes cap the CPU and GPU clocks and the number of active cores. Check the current mode with sudo nvpmodel -q, list the modes your JetPack defines in /etc/nvpmodel.conf, and switch with sudo nvpmodel -m followed by the mode number; on the Orin Nano Super the modes run from about 7 W up to 25 W (MAXN SUPER). sudo jetson_clocks then locks the clocks at the maximum of that mode, which gives steady timing for benchmarks; it does not survive a reboot.

Heat decides whether that speed lasts. The developer kit has a heatsink and fan; in an enclosure, give the fan a clear path for air in and out. Watch the temperatures in tegrastats or jtop during a long run: if the clocks drop while the temperature is high, the chip is throttling and the enclosure needs more airflow. Test at the hottest room temperature you expect, not on a cool desk.

For a device in the field, size the power supply for the mode you use plus the cameras and USB devices, with margin. Measure your real energy use: a Jetson averaging 15 W uses 15 × 24 = 360 Wh a day. Plan recovery too: run your program as a systemd service with restarts, enable a hardware watchdog if your carrier supports it, keep logs off the boot disk, and make sure the device comes back on its own after a power cut.

Power modes trade speed for heat

A Jetson has preset power modes, selected with nvpmodel, that set the power limit, the number of active CPU cores and the clock speeds. A lower mode runs cooler and lasts longer on a battery or a small supply, and a higher one gives more speed. The jetson_clocks tool pins the clocks at their maximum, which helps when you are measuring speed fairly but makes more heat.

Check the current state with tegrastats, which shows the load, memory, temperatures and power of each part while your program runs.

Heat and throttling

When the chip gets too hot, the Jetson lowers its clocks to protect itself, and your frame rate drops with no error message. If a model runs fast at first and slows after a few minutes, suspect throttling and check the temperature. A fan and a heatsink, plus air that can move around the unit, are part of the design, not an option, in an enclosure or in sun.

Use a supply that can deliver the rated power. A supply that sags causes resets or reduced performance under load.

Field deployment

Plan for an unattended device. Run the program as a service so it starts after power returns, limit logging so the storage does not fill, and use a fast, reliable drive instead of a cheap card for a system that writes often. Test the whole setup at the hottest temperature you expect, running the real workload for hours.

Common mistakes
  • Measuring speed in one power mode and deploying in another.
  • Not noticing throttling because no error is shown.
  • Putting the unit in a closed box with no airflow.
Advanced lesson · Pro plan

Practise this lesson with Pro

The explanation above is free for everyone. The practice for Advanced lessons in every domain are part of the Pro plan at ₹999 a month.

With Pro you also get: a worked example, a hands-on task, a 3-question check.

Common questions

What will I learn in "Jetson Power Modes, Heat and Field Deployment"?

Choose a power mode, keep the Jetson cool and plan power and recovery for a device in the field.