ARM-Big-Little

Arm big.LITTLE combines CPU cores with different performance and energy characteristics in one system. The approach uses a common software architecture while providing different execution implementations. Arm’s history dates its introduction to 2011. The design goal is to place work on suitable cores rather than assume that one core configuration is optimal for every task.

A high-performance core and an efficiency-oriented core make different trade-offs. Execution width, pipeline organization, caches, and operating frequency influence both latency and power. The smaller core is not defined simply by running the same physical design at a lower clock. Architectural compatibility allows software to use distinct implementations within a coordinated platform.

Arm big.LITTLE Conceptual comparison; not a manufacturing specification or scale drawing Common software view Architecturally compatible cores Different execution designs Core choices High-performance engine Efficiency-oriented engine System policy Task placement and migration Latency / energy / thermal balance Compatible instruction behavior permits different core implementations; scheduling determines how their trade-offs are used.

Scheduling determines how the hardware opportunity becomes useful. Interactive bursts, background services, and sustained parallel work have different requirements. Moving work can introduce migration, cache, and coordination costs. The operating system needs an appropriate policy and an accurate view of workload demand and system state.

The implementation model evolved across products and generations. Different systems can use cluster migration or more flexible concurrent scheduling arrangements. Shared memory, interconnect coherence, and power domains also vary. The big.LITTLE name alone therefore does not specify exactly how many cores run at once or how work is assigned.

The correct outcome measure is completed work and energy under realistic use. A peak benchmark on the largest cores does not establish standby behavior or battery runtime. Conversely, low idle power does not guarantee acceptable response time. The approach illustrates the coordination of heterogeneous CPU design with scheduling, power control, and application behavior.

Sources and further reading. [Arm official technology history](https://newsroom.arm.com/blog/arm-official-history); [Arm 2012 big.LITTLE announcement](https://www.arm.com/company/news/2012/01/media-alert-arm-biglittle-technology-wins-linley-analysts-choice-award).

Read Arm big.LITTLE as a heterogeneous CPU strategy that coordinates different core designs to match changing performance and energy demands.

Take arm-big-little further

Ask the copilot about this term, or have our engineers assess it against your process.