Workload and traffic model
Turn core counts and clock targets into a workload model with dependencies, cache misses and sharing. Core count alone does not establish instructions per cycle or application throughput.
AMD / SILICON DESIGN
A Zen 2 compute die is a reusable part of a processor package. Core changes, cache grouping, and separate I/O silicon explain its engineering significance.

Original source · Retrieved not recorded
FritzchensFritz · photographer · Included in this image
No copyright attribution condition under CC0; source credit retained for provenance.
Ryzen 5 3600 CCD specimen identified by the original photographer. The image shows one compute die within the processor package.
An isolated CPU compute die photographed diagonally against a black background.
| Identity & fabrication | |
|---|---|
| Record year | Manufacturer / primary sourceAMD / Hot Chips Scope: physical core-complex die Source date: 2019-08-19 Year basis: technical disclosure. This is distinct from source publication and record update. |
| Packaging, power & physical analysis | |
| Die area | Manufacturer / primary sourceAMD / ISSCC; uploaded by AMD Scope: One Zen 2 7nm CPU Core Complex Die (CCD), design-level disclosure Source date: 2020 Samuel Naffziger presentation. Excludes the separate client/server I/O die and package. No x/y dimensions disclosed. |
| Additional specifications | |
| CCXs per CCD | Manufacturer / primary sourceAMD / Hot Chips Scope: physical core-complex die Source date: 2019-08-19 Conference PDF is indexed but exceeds web viewer size limit; fields use its indexed slide text. Do not infer enabled product cores from this design record. |
| Maximum L3 per CCX | Manufacturer / primary sourceAMD / Hot Chips Scope: physical core-complex die Source date: 2019-08-19 Conference PDF is indexed but exceeds web viewer size limit; fields use its indexed slide text. Do not infer enabled product cores from this design record. |
Start with documented specifications, then use the study prompts below. The prompts are engineering guidance, not a claim about this product’s private RTL or physical implementation.
Turn core counts and clock targets into a workload model with dependencies, cache misses and sharing. Core count alone does not establish instructions per cycle or application throughput.
Choose a representative producer/consumer path and specify acceptance, ordering, backpressure, outstanding capacity and reset recovery. Turn these contracts into assertions and test scenarios before optimizing the datapath.
Obtain macro abstracts, pin maps, timing libraries and activity-based power estimates. Explore macro proximity, routing channels and power-grid reachability together. An annotated die photograph can suggest study questions, but cannot supply a netlist, PDK or signoff constraints.
TECHNICAL ARTICLE
A Zen 2 compute die is a reusable part of a processor package. Core changes, cache grouping, and separate I/O silicon explain its engineering significance.

AMD’s ISSCC chiplet presentation identifies a 74 mm², 7nm core-complex die and separately identifies client and server I/O dies. Its package diagrams place these components in Ryzen, EPYC, and Threadripper arrangements. The photographed CCD is therefore not the whole processor. External memory interfaces and package-level connections must be interpreted through the appropriate product’s I/O die and package, rather than assigned to this compute photograph.
AMD’s core presentation describes a four-core CCX with 16 MB of L3 in the desktop/server configuration and 512 KB of L2 per core. Its Hot Chips cache diagram places two CCXs in a CCD and identifies an Infinity Fabric die-to-die interface. The core presentation also shows smaller L3 configurations for other uses of Zen 2. VLSI Museum interpretation: a microarchitecture name does not imply one universal cache topology. The desktop/server CCD record must retain its own configuration, and software locality questions should start with the documented cache-sharing group.
AMD’s Zen 2 historical overview describes a new TAGE branch predictor, an operation cache enlarged to 4K operations, and floating-point datapaths widened to 256 bits. VLSI Museum interpretation: these changes address different parts of the work-supply chain. Prediction selects the path to fetch, the operation cache can supply previously decoded work, and execution width determines what that supplied work can do. Wider arithmetic alone cannot guarantee higher application throughput.
The ISSCC core disclosure describes repeated L3 slices, multiple stages of clock gating, and local regulators supplying the L2 and L3 arrays. These implementation details explain why doubling a cache is more than adding storage bits: clock distribution and memory-array supply must remain workable. This is vendor-documented implementation context; it does not establish the coordinates of those structures on the Museum’s particular optical photograph.
The Ryzen 5 3600 specification lists six enabled CPU cores, twelve threads, 32 MB of L3, an AM4 socket, and TSMC 7nm FinFET technology for its CPU cores. These values belong to the complete product. VLSI Museum interpretation: the socket describes the packaged processor’s platform connection, not a socket into which a bare CCD can be installed. Enabled product cores must also remain distinct from the reusable die design.
TSMC documents N7 as its 7nm FinFET technology entering volume production in 2018, and distinguishes N7+ as a later process using EUV lithography. That distinction prevents a generic seven-nanometre label from silently becoming an EUV claim. VLSI Museum interpretation: the linked foundry page establishes process-family context, while the AMD specification establishes this product’s stated CPU-core technology. An exact manufacturing variant needs its own explicit evidence.
Photographed Ryzen 5 3600 specimen. The complete package also contains an I/O die; no unverified layout is shown.
Wikimedia Commons · FritzchensFritz · EvidenceSlide 2 identifies the CCD and Zen 2 cores.
AMD / ISSCC; uploaded by AMD · EvidenceThis source supports the cited sections of the technical exhibit; access scope is recorded with the source.
AMD / Hot Chips · EvidenceThis source supports the cited sections of the technical exhibit; access scope is recorded with the source.
AMD / ISSCC; uploaded by AMD · EvidenceThis source supports the cited sections of the technical exhibit; access scope is recorded with the source.
AMD / ISSCC; uploaded by AMD · EvidenceThis source supports the cited sections of the technical exhibit; access scope is recorded with the source.
AMD · EvidenceThis source supports the cited sections of the technical exhibit; access scope is recorded with the source.
AMD · EvidenceThis source supports the cited sections of the technical exhibit; access scope is recorded with the source.
TSMC · EvidenceWikimedia Commons · FritzchensFritz
Ryzen 5 3600 CCD specimen identified by the original photographer. The image shows one compute die within the processor package.
Link not yet checked
View original die photoAccess to a source does not grant permission to reproduce its images.
AMD ZEN 2 — Hot Chips 31 ↗ · AMD / Hot Chips
AMD Ryzen 5 3600 — Zen 2 / Matisse CCD ↗ · Wikimedia Commons · FritzchensFritz
AMD Chiplet Architecture for High-Performance Server and Desktop Products ↗ · AMD / ISSCC; uploaded by AMD