← Back to the chapter · Previous detail · Next detail →
Technical detail · Energy Cost of Common Operations
Compare added local charge with avoided downstream charge
Local work saves energy when it removes a larger downstream cost. A filter can be worthwhile if it prevents a radio session. Compression can be worthwhile if saved airtime and retries exceed compute and memory cost. Aggregation can be worthwhile if a summary is as useful as raw samples. The same choices fail when they add active time without reducing expensive operations or when they damage the information the system needs.
The useful comparison is not CPU cycles versus bytes in the abstract. Compare charge per useful report under the same firmware, sensor configuration, radio environment, and error policy. If the optimization changes retry behavior, storage pressure, clock state, or wake duration, include those effects in the full-cycle trace.
A break-even point is where the added and avoided costs are equal. A useful test is added local charge < removed downstream charge, with service quality held constant. For example, compression that adds 15 ms at 12 mA costs 0.18 mA-s. If it prevents an 80 mA, 250 ms extra radio retry, it saves 20 mA-s and is worth measuring further. If retries, receive windows, and active duration stay unchanged, the smaller payload has not yet proved an energy win.