Duty cycling is a power management technique where a device, such as a radio, sensor, or processor, periodically alternates between a short, high-power active state and a long, low-power sleep state. The duty cycle, expressed as a percentage, is the ratio of active time to the total period of one on/off cycle. This method dramatically reduces average power consumption by ensuring components only draw significant current when performing essential work, making it critical for TinyML and Internet of Things (IoT) deployments with strict energy budgets.
Glossary
Duty Cycling

What is Duty Cycling?
A foundational power-saving technique for battery-operated and energy-harvesting edge devices.
In TinyML systems, duty cycling is applied to the entire inference pipeline. A microcontroller's main core and peripherals remain in deep sleep until a scheduled timer or an external wake-on-event trigger activates them. Upon waking, the system rapidly powers sensors, collects data, executes a compressed neural network inference, and may transmit a result via radio before returning to sleep. Optimizing the duty cycle involves balancing the energy cost of each wake-up against the latency and freshness requirements of the application, a key part of energy-constrained scheduling.
Key Characteristics of Duty Cycling
Duty cycling is a fundamental power management technique where a device alternates between short, active operational periods and long, low-power sleep states. The ratio of active time to total cycle time defines the duty cycle, directly governing energy consumption.
Duty Cycle Definition & Calculation
The duty cycle (D) is the fraction of time a component is active within a total period (T). It is calculated as D = T_active / T_total. A 1% duty cycle means the device is active for 1 ms every 100 ms. This metric is the primary lever for energy savings, as power consumption scales linearly with D when sleep power is negligible. For example, a radio consuming 100 mA at 3.3V when active and 1 µA when asleep achieves an average current of ~3.3 mA at a 1% duty cycle, a 30x reduction.
Active & Sleep State Power Profiles
Duty cycling exploits the disparity between two distinct power states:
- Active State: Full operational power (P_active). The device performs computation, sensing, or communication. Power is dominated by dynamic switching current.
- Sleep/Low-Power State: Minimal static power (P_sleep). Non-essential circuits are clock-gated or power-gated. Only critical functions like a real-time clock or wake-up logic remain active. The average power is P_avg = (D * P_active) + ((1-D) * P_sleep). Effective duty cycling requires P_sleep to be orders of magnitude smaller than P_active.
Trade-off: Latency vs. Energy
Duty cycling introduces a fundamental trade-off. Lowering the duty cycle saves energy but increases latency and response time. A device asleep cannot respond to events until its next scheduled wake-up. This is managed by:
- Fixed Periodic Wake-ups: Predictable latency, simple to implement.
- Wake-on-Event: Uses an always-on (AON) domain with ultra-low-power comparators to wake the main system only when a sensor threshold is breached, minimizing latency for critical events without constant polling.
Application to Radios & Communication
This is the most common use case in IoT. Radios (e.g., BLE, LoRa, WiFi) are extreme power consumers. Duty cycling protocols define synchronized active windows:
- Low-Power Listening: Receiver wakes up briefly to check for a preamble signal.
- Scheduled Rendezvous (TSCH): Nodes align their active slots using a shared schedule. The goal is to minimize the time the high-power radio transmitter and receiver are on. A wake-up radio (WuR) is a specialized ultra-low-power receiver that listens continuously for a magic packet to trigger the main radio, enabling near-zero latency while maintaining a near-0% duty cycle for the main radio.
Application to Sensors & Sampling
Sensors are duty-cycled to avoid continuous analog-to-digital conversion. The adaptive sampling rate is a key technique:
- Sample frequently (high D) during periods of interest or high activity.
- Sample infrequently (low D) during quiescent periods. For instance, an accelerometer might sample at 100 Hz when motion is detected but drop to 1 Hz during stillness. This requires an event detection circuit in the AON domain to classify the signal and trigger the sampling rate change, ensuring no events are missed.
System-Level Coordination & Scheduling
Effective duty cycling requires coordinating multiple subsystems (sensor, processor, radio). Power-aware scheduling ensures all components are active simultaneously to complete a task before returning to sleep. Poor coordination causes cascading active periods, wasting energy. The sequence for a sensing node is often:
- Wake up processor and sensor (from sleep).
- Sample and process data.
- Power up radio, transmit data, power down radio.
- Return all components to sleep. The goal is to minimize the time any high-power component is active and to batch operations within the shortest possible active window.
Duty Cycling vs. Other Power Management Techniques
A feature comparison of duty cycling against other core power-saving strategies used in TinyML and embedded systems.
| Feature / Metric | Duty Cycling | Dynamic Voltage & Frequency Scaling (DVFS) | Power Gating |
|---|---|---|---|
Primary Power Savings Target | Dynamic power of radios & sensors | Dynamic power of CPU/accelerator | Static (leakage) power of idle blocks |
Granularity of Control | Component or subsystem (e.g., radio) | Processor core or cluster | Logic block, SRAM bank, or core |
Typical Activation Latency | Milliseconds to seconds | Microseconds to milliseconds | Tens to hundreds of microseconds |
Energy-Accuracy Trade-off | Sampling/communication fidelity | Inference latency & throughput | None (functionality preserved) |
Hardware Overhead | Low (timers, state machine) | Medium (voltage regulators, PLLs) | High (header/footer switches, isolation cells) |
Use Case Paradigm | Event-driven or periodic sensing | Load-proportional computing | Long-term idle periods |
Software Control Interface | Application timer or RTOS task | OS governor or firmware API | Firmware or power management unit (PMU) |
Synergy with Duty Cycling |
Frequently Asked Questions
Duty cycling is a foundational power-saving technique for battery-powered and energy-harvesting edge devices. These questions address its core principles, implementation, and trade-offs for TinyML engineers.
Duty cycling is a power management technique where a device, such as a radio, sensor, or microcontroller, periodically alternates between a short active state and a long low-power sleep state. The duty cycle is defined as the ratio of active time (T_active) to the total cycle period (T_active + T_sleep), expressed as a percentage. For example, a 1% duty cycle means the device is active for 1ms and sleeps for 99ms in a 100ms cycle. The core mechanism involves a low-power timer or a Real-Time Clock (RTC) in the always-on (AON) domain waking the main processor at precise intervals to perform a task before returning to sleep. This dramatically reduces average power consumption, as the static and dynamic power draw during sleep is orders of magnitude lower than during active computation or communication.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Duty cycling is a core technique within a broader ecosystem of hardware and algorithmic strategies for minimizing energy consumption in embedded systems. These related concepts define the landscape of power-aware TinyML.
Dynamic Voltage and Frequency Scaling (DVFS)
A hardware-level power management technique that dynamically adjusts a processor's operating voltage and clock frequency in response to real-time computational workload. This reduces dynamic power consumption, which scales with the square of the voltage and linearly with frequency. In TinyML, DVFS can be applied during inference to match the compute intensity of different neural network layers.
Power Gating
A circuit design technique that uses header or footer switches to completely cut off the power supply (VDD or GND) to an idle logic block, core, or memory bank. This eliminates both dynamic power and static leakage power, offering the deepest power savings. It is often used in conjunction with duty cycling to power down entire subsystems during long sleep periods, but incurs a significant latency and energy cost to restore power and state.
Clock Gating
A fundamental power-saving technique that disables the clock signal to portions of a digital circuit when they are not performing useful computation. This eliminates the dynamic power dissipation caused by unnecessary clock toggling (charging and discharging of capacitive loads). It is a finer-grained, lower-latency technique than power gating and is ubiquitously employed in processor design and neural network accelerators to gate clocks to idle arithmetic logic units (ALUs) or memory arrays.
Wake-on-Event
A critical system feature that enables duty cycling by allowing a device in a deep sleep state to be awakened by a specific, low-power external trigger. This trigger is monitored by an Always-On (AON) Domain. Common triggers include:
- A sensor reading exceeding a predefined threshold.
- A specific pattern from a Wake-up Radio (WuR).
- A timer expiration (for periodic duty cycling). This mechanism is essential for creating responsive, ultra-low-power sensing applications.
Always-On (AON) Domain
A small, isolated, and ultra-low-power section of a System-on-Chip (SoC) that remains powered and active even when the main processor, memory, and other subsystems are in a deep sleep or power-gated state. Its responsibilities include:
- Monitoring simple sensors or Wake-on-Event triggers.
- Maintaining a real-time clock (RTC).
- Managing the wake-up sequence for the main processor. The AON domain is the "watchdog" that makes intelligent, scheduled duty cycling possible.
Energy-Neutral Operation
A design goal and operational paradigm for systems powered by energy harvesting (e.g., solar, thermal, RF). The system is designed so its long-term average energy consumption is less than or equal to the average energy harvested from the environment. Duty cycling is the primary knob to achieve this balance. The system must dynamically adjust its active duty cycle based on available energy to enable theoretically perpetual operation without a battery.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us