← Back to Overview
Compute Tile · Intel 04A · DP Core · Architecture Deep Dive
SUNSET
COVE

The IPC workhorse of the Eventide generation. The highest instruction-per-clock throughput of any core in the lineup — and the core that reintroduces Hyper-Threading to Intel's P-core class for the first time since Lion Cove removed it.

Intel 04A · 0.4nm-class GAA P-SMT · 2T Per Core · Returns 10-Wide Decode — Widest On-Chip 720-Entry ROB 20 Disjoint Execution Ports No V8 HyperBOOST
+38%
IPC Over PTL P-Core
highest IPC in lineup
10W
Decode Width
widest on-chip
720
ROB Entries
deepest OOO window
+92%
MT Throughput vs PTL
P-SMT · 2T · disjoint ports
The IPC Workhorse

The Sunset Cove Dense Performance core takes the opposite architectural bet from the UHP Solar Eclipse. Where Solar Eclipse pursues frequency headroom at the expense of instruction-level depth, Sunset Cove maximizes IPC — instructions per clock cycle — across every execution unit in the design. It is the core in the Eventide lineup that extracts the most useful computation from every cycle that elapses, regardless of what that clock frequency is.

The headline numbers reflect this: +38% IPC over the Panther Lake P-core (Cougar Cove), which was itself a significant IPC improvement over its predecessors. At the same operating frequency, a Sunset Cove core completes 38% more work per cycle than the last-generation flagship. This is an architectural achievement that comes from three compounding decisions: the widest decode front-end on the chip, the deepest out-of-order execution window, and the most ambitious multi-porting strategy in recent x86 history.

The Sunset Cove is also the core that makes one of the most architecturally significant reversals in recent Intel history: the reintroduction of Hyper-Threading to the P-core class. Intel removed SMT from its Performance cores starting with Lion Cove in Lunar Lake, citing the latency and execution port contention problems that traditional SMT introduced. Sunset Cove re-adds it — but with a fundamentally re-engineered implementation that specifically addresses those prior criticisms.

FULL CORE SPECIFICATION
Core classDP — Dense Performance
CodenameSunset Cove
Process nodeIntel 04A · 0.4nm-class GAA
Base clock2.1 GHz
Max turbo5.2 GHz
SMTP-SMT · 2 threads/core
Logical threads2× physical core count
Decode pipeline width10-wide (widest on-chip)
OOO ROB depth720 entries
Execution ports20 — dual-thread aware
Port allocation modelDisjoint — no thread contention
L0 extra-LLC cache128 KB / core
L2 private cache6 MB / core (largest on-chip)
V8 HyperBOOSTNot supported
IPC classHighest on-chip
TD dispatch classClass 2 — IPC-Bound MT
P-SMT 2T AVX-512 AMX VNNI2 CET ENQCMD TSX-NI CLDEMOTE
P-SMT Returns — Zero Port Contention
Why Intel Removed SMT — And Why It's Back

Intel's original Hyper-Threading, as implemented through Alder Lake and prior generations, shared execution ports between the two hardware threads on each P-core. When both threads were running instructions that needed the same execution unit at the same time, one thread had to wait. The result was a technology that provided genuine multi-thread throughput in some workloads, but introduced latency unpredictability in others — particularly in latency-sensitive gaming scenarios where thread contention caused frame time variance. Lion Cove in Lunar Lake removed SMT entirely from P-cores for this reason. The simplification improved single-thread predictability and reduced power, and for Lunar Lake's efficiency-first mission, that was the right call.

Sunset Cove re-adds SMT, but with a different design: P-SMT uses disjoint execution port allocation. The two hardware threads on a Sunset Cove core do not share execution ports. Each thread is assigned a dedicated subset of the 20-port execution array. There is no runtime arbitration between threads for port access, no contention latency, and no head-of-line blocking. The result is SMT that genuinely behaves like having two narrower cores within one core's die footprint — the instruction throughput per mm² is exceptional, without the latency pathologies that got SMT removed in the first place.

THREAD 0 — DEDICATED PORTS
Integer ALU (×4 dedicated)
FP / Vector units (×2)
Load port (×2)
Store port (×1)
AGU (×1)
THREAD 1 — DEDICATED PORTS
Integer ALU (×4 dedicated)
FP / Vector units (×2)
Load port (×2)
Store port (×1)
AGU (×1)
20 execution ports total · no inter-thread contention · disjoint allocation enforced in hardware

The 20-port execution array is the physical implementation of the P-SMT promise. At 20 ports across a dual-thread design, each thread effectively has access to the equivalent of a 10-port out-of-order engine — which, for reference, is wider than the execution arrays of most prior-generation Intel P-cores. This is not a compromise configuration. This is a dual high-performance execution engine housed in a single core.

The 720-entry Reorder Buffer is the other key enabler. The ROB is the OOO window — it defines how many instructions ahead of the current commit point the processor can speculatively execute. A 720-entry ROB means the Sunset Cove can have 720 in-flight micro-operations at once across both hardware threads. This deep speculative window allows the core to continue finding work to do even when individual threads are waiting on memory accesses, branch misprediction recovery, or long-latency instructions. For multi-threaded workloads where both threads are executing non-trivially, this is where the +92% MT throughput figure comes from.

The 128 KB L0 extra-LLC is the largest on-chip L0 in the Eventide lineup — larger than the Solar Eclipse's 96 KB — because a 10-wide decode front-end serving two threads simultaneously has proportionally higher instruction fetch bandwidth requirements. The 6 MB private L2 is similarly the largest per-core L2 in the lineup, reflecting the working set pressure that two active threads generate.

10-Wide Decode, 720-Entry ROB
SUNSET COVE · P-SMT PIPELINE DIAGRAM
INST FETCH TBM 5.0 · dual-thread BRANCH PRED per-thread predictor 10-WIDE DECODE 10 instr/cycle → µOPs widest on-chip ↑ µOP CACHE / LOOP STREAM DETECTOR · DUAL-THREAD AWARE 128KB L0 feeds both threads simultaneously P-SMT THREAD ARBITER Thread 0 + Thread 1 · disjoint port allocation · no contention RENAME T0 / ROB 720-entry · shared window RENAME T1 / ROB shares 720-entry ROB pool T0 EXEC PORTS (10 disjoint) ALU·FP·Vec·Ld·St · no sharing T1 EXEC PORTS (10 disjoint) ALU·FP·Vec·Ld·St · no sharing RETIRE / WRITEBACK — UNIFIED in-order commit from 720-entry ROB · both threads L2 PRIVATE CACHE · 6 MB / CORE (LARGEST IN LINEUP) miss → Kache Kore™ bLLC via FOveros 2.0

The Sunset Cove carries the largest private cache of any core in the Eventide lineup. The 128 KB L0 extra-LLC, the 256 KB private L1, and the 6 MB private L2 are all sized for the bandwidth requirements of two active hardware threads simultaneously feeding a 10-wide decode front-end. L2 misses are absorbed first by the 12 MB Compute Tile shared L3 before reaching the photonic fabric.

L0
L0 Extra-LLC 128 KB / core
Largest L0 in lineup — feeds 10-wide decode under dual-thread load
↓ miss
L1
L1 I-Cache + D-Cache 256 KB / core
↓ miss
L2
Private L2 Cache 6 MB / core
Largest per-core L2 on-chip — 6 MB shared across 2 hardware threads
↓ miss
L3
Compute Tile Shared L3 12 MB / tile · 48 MB total
Shared across all UHP + DP + SPE cores on Compute Tile — 4 tiles × 12 MB
↓ miss → FOveros 2.0 photonic
L4
Kache Kore™ bLLC 4 GB · APU-shared
Shared across all CPU + GPU + NPU tiles via photonic fabric
Gen-on-Gen Performance · vs Panther Lake P-Core (Cougar Cove)
IPC — single-thread
+38%
MT throughput
+92%
Perf/W (multi-thread)
+44%
ROB depth increase
+2.4×
Where IPC Is Everything

The Sunset Cove core is the Hardware Thread Director's choice for workloads that are IPC-bound and multi-threaded simultaneously — scenarios where raw instruction throughput per core matters more than frequency headroom or core density. These are the workloads where the 720-entry ROB, 20-port disjoint execution array, and P-SMT combine into a result that no single-threaded or density-optimized core can match.

⚙️
Thread Director Classification
Class 2 — IPC-Bound MT. Thread Director routes threads here when instruction-level parallelism is high and working set fits in the large L2 hierarchy.
🧵
P-SMT Always Active
Unlike prior SMT implementations, P-SMT does not degrade single-thread performance due to disjoint port allocation. Both threads can run simultaneously at full execution width.
📐
Deep OOO Window
720-entry ROB finds useful work across 720 in-flight instructions, masking memory latency and long-latency operations far more aggressively than shallower OOO designs.
🧮
AMX + AVX-512 Full Width
Both hardware threads have dedicated access to full-width VNNI2 and AMX matrix acceleration units. No sharing, no throughput division — full acceleration for both threads simultaneously.
💼
Productivity Workloads
Spreadsheet computation, document processing, and background application load all benefit from IPC. Highest throughput per active cycle of any core.
🐍
Runtimes & Scripting
Python, Node.js, Ruby — interpreted and JIT environments are IPC-bound. The deep OOO window handles irregular instruction patterns that frustrate shallower designs.
📊
Local AI Inference
Token generation in LLM inference is memory-bandwidth and IPC limited. P-SMT + AMX + 6 MB L2 + Kache Kore™ bLLC create an optimal local inference environment.
🏗️
Server-Class MT
With P-SMT active, the X500 SKU's Sunset Cove population delivers server-grade multi-thread density in a mobile chassis. Enterprise workloads that expect Xeon-class MT now have a mobile answer.