July 30, 2026
Battery drama in tiny-chip land
ESP32-C6 Power Consumption: Arduino vs. Zephyr vs. ESP-IDF Comparison
This tiny chip power test sparked a "Arduino is wasteful" pile-on
TLDR: A careful test found that software choice changes how much power an ESP32-C6 chip uses even before you add fancy battery-saving tweaks. Commenters instantly turned it into a blame game, with Arduino getting side-eye and some declaring the whole ESP32 line bad at saving power.
A fresh power-use faceoff for the ESP32-C6 should have been a dry engineering comparison. Instead, the comments turned it into a full-blown framework fight night. The test compared three popular ways to program the same small internet-connected chip: Arduino, Zephyr, and ESP-IDF. The setup was careful and boring in the best possible way: same board, same power source, same tiny tasks, and no special battery-saving tricks switched on. That last detail mattered a lot, because the numbers were about each system’s default behavior when left awake, not their best-case sleeping mode.
And that’s where the crowd pounced. The loudest reaction was basically: well, duh. One commenter shrugged that Arduino burning extra power in an idle loop is “not particularly uncommon,” which is the engineering version of a devastating eye-roll. Another went even harder, declaring, “ESP32 never was good for any powersaving applications,” a spicy blanket statement guaranteed to start arguments. Meanwhile, architecture fans used the moment to celebrate the chip family’s move to RISC-V, with one comment dunking on the old design as “non-standard” and “not missed.”
Even the optimization debate got its own mini-drama. One commenter warned that chasing speed settings can backfire because bigger code can stress the chip’s tiny memory and hurt efficiency. And in peak nerd-comedy fashion, someone half-derailed the thread to rave about power analyzers like they were reviewing kitchen gadgets. Classic comment section energy: less ‘what happened,’ more ‘here’s my manifesto.’
Key Points
- •The article compares ESP32-C6 power consumption across Arduino, Zephyr RTOS, and ESP-IDF under default out-of-the-box conditions.
- •Testing used an ESP32-C6 Development Board powered at 3.6V by an Otii Ace, with synchronized capture of current, power, voltage, and UART RX.
- •The methodology separates SDK overhead from user code through Empty, Reference, and Active Workload scenarios including LED blink, CRC8, and floating-point multiplication.
- •Wi‑Fi and BLE were not initialized, and no sleep modes such as light-sleep or deep-sleep were enabled during the tests.
- •A Python-based automation framework using the Otii TCP API executed five 60-second iterations per workload, with 20-second power-off cooldowns and steady-state data isolation.