Xbox 360 CPU Deep Dive: 3.2 GHz PowerPC Tri-Core "Xenon" Architecture

The Xbox 360 runs on a custom IBM PowerPC "Xenon" tri-core processor clocked at 3.2 GHz. Here's the technical breakdown.

Technical Specifications

Architecture: 64-bit PowerPC (Power ISA 2.03), in-order execution (no out-of-order / branch prediction).
Cores: 3 symmetric cores (PPE — PowerPC Processing Elements).
Threads: 2 hardware threads per core (SMT) → 6 logical threads total.
Clock: 3.2 GHz (all cores).
L1 Cache: 32 KB Instruction + 32 KB Data per core.
L2 Cache: 1 MB Shared (arbitrated across 3 cores).
FLOPS (Theoretical Peak): ~76.8 GFLOPS (Vector VMX-128 / AltiVec per core).
Process Nodes: 90 nm (Xenon) → 65 nm (Zephyr/Falcon) → 45 nm (Jasper) — same clock, lower power/heat.

In-Order Limitation: Branch mispredicts stall the pipeline heavily. Compilers (Microsoft XDK) were critical for instruction scheduling.
VMX-128 (AltiVec+): 128-bit SIMD × 2 per core → 6×128-bit vectors/cycle. Heavy math (physics, skinning, audio) offloaded here.
Compared to Modern CPUs: Roughly ~1/10th single-thread performance of a Ryzen 5 5600 / i5-12400. But the fixed platform allowed deep optimization (assembly, custom allocators, SPU-like SPE usage on GPU via MEMEXPORT).
Backward Compatibility on Xbox One: Jaguar 8-core @ 1.75 GHz has higher total throughput but lower single-thread. 360 games run via emulated Xenon cores (JIT recompilation) + GPU translation.

Codename	CPU Process	GPU Process	Wattage	RROD Risk
Xenon (Launch)	90 nm	90 nm	203 W	Very High
Zephyr (HDMI added)	90 nm	80 nm	175 W	High
Falcon	65 nm	80 nm	150 W	Medium
Jasper	65 nm	65 nm	135 W	Low
Trinity (Slim)	45 nm	45 nm	100–120 W	Very Low
Corona (E Model)	45 nm	45 nm	90–100 W	Very Low

Identify Yours: Check the back label → 12.1 A = Jasper (Best Fat). 10.83 A / 9.6 A = Trinity/Corona (Slim/E).

Xbox 360