---
title: "The power budget is the design constraint"
url: "https://kyberlinux.com/blog/the-power-budget-is-the-design-constraint"
description: "On battery-powered and fanless hardware, watts spent by the system are watts not spent on the model. Idle draw is a design decision, not an accident."
---

# The power budget is the design constraint

August 4, 2026·3 min read·Kyber Linux

On a server nobody notices the operating system’s own consumption. On a device in a pocket, a robot on a battery or a fanless box on a shelf, every watt the system spends on itself is a watt not available to the model, and it compounds into fewer hours of runtime, more thermal throttling and a bigger enclosure. Power is not a metric you optimise at the end. It is the constraint the rest of the design has to fit inside.

## Where the watts actually go

Not where people assume. Inference is bursty and expensive, and it is also the part you wanted. The interesting waste is elsewhere.

**Wake-ups.** A CPU that never reaches a deep sleep state costs more than one doing occasional work. A dozen daemons each polling on their own timer, none of them expensive individually, can keep a processor awake permanently. Aligning or removing timers is often worth more than any optimisation inside the workload.

**Services you did not ask for.** Indexers, telemetry agents, update checkers, discovery protocols. On a general distribution these are reasonable defaults. On a device with one job they are a background tax paid every second of every day.

**Memory pressure.** Swap and cache churn cost power in a way that does not look like power in any monitoring tool. A model whose weights nearly fit is far more expensive than one that fits.

**The radio.** On carried hardware, networking often dominates. Every avoidable round trip is power, which is a second argument for local inference alongside latency and privacy.

## Idle is the number that matters

Peak consumption is what gets published and what nobody experiences. The number that decides battery life is what the device draws when it is doing nothing, because that is most of its existence.

A device that draws meaningfully less at rest gets a longer runtime on the same battery, or the same runtime on a smaller one — which changes the industrial design, the weight and the price. That chain is why idle draw belongs in the design brief rather than in a later optimisation pass.

We publish idle draw per reference image for exactly this reason. A single headline number for “the OS” would be meaningless without naming the hardware and the workload, and anyone quoting one without both is telling you very little.

## What a system can actually do about it

**Ship less.** Every service that does not exist consumes nothing. This is the same argument as minimalism for security, arriving at the same conclusion from a different direction — which is usually a sign the conclusion is right.

**Align the wake-ups.** Batch periodic work so the processor gets long uninterrupted sleep rather than being poked every few hundred milliseconds by unrelated timers.

**Let the scheduler see thermal state.** On fanless hardware, thermal headroom determines what is possible in the next minute. A scheduler that treats it as an input can slow a background task now rather than throttle an interactive one later.

**Size the model to the device.** The biggest single lever, and not really an OS decision — but the system should make it easy to know what a given model actually costs to keep resident.

## The honest limits

An operating system cannot make a model cheap. If the workload wants an accelerator running flat out, that is the power budget, and no amount of careful daemon management changes it.

What the system controls is the overhead: what is running when nothing is happening, how quickly the machine gets back to sleep, and whether the scheduler knows that thermal headroom is a resource. On a server that overhead is a rounding error. On a device someone carries all day, it is the difference between a product and a prototype.

-   power
-   edge
-   thermal
-   efficiency

## Keep reading

-   [Why a general-purpose distribution is the wrong base for AI](https://kyberlinux.com/blog/why-a-general-purpose-distro-is-the-wrong-base)
-   [Immutable, verified, boring](https://kyberlinux.com/blog/immutable-verified-boring)