Course map
- 1 lesson
Starts with Architecture Metrics Reference
- 1 lesson
Starts with Workload Taxonomy for Architects
- 1 lesson
Starts with Architecture Glossary
- 1 lesson
Starts with Computer Architecture Cheatsheet
- 14 lessons
Starts with The Five-Stage Datapath
- 15 lessons
Starts with Address Decode and the Access Path
- 6 lessons
Starts with Topology Families Compared
- 9 lessons
Starts with MESI States and the Single-Writer Invariant
- 9 lessons
Starts with What a PMU Counts
- 6 lessons
Starts with When an Accelerator Pays Off
- 9 lessons
Starts with PPA Budget Ledger
- 14 lessons
Starts with Architecture Whiteboard Framework
About this course
This course connects each workload to the structure it stresses and the metric that exposes the bottleneck. Sixteen topics and eighty-two lessons cover that chain from pipeline to signoff.
The eight parts
Part | Topics | Lessons | Content |
|---|---|---|---|
3 | 14 | How pipelines, branches, and out-of-order issue set IPC. | |
3 | 15 | Caches, bandwidth, and virtual memory from AMAT to TLB reach. | |
1 | 6 | Topology, routing, flow control, and QoS for on-chip networks. | |
2 | 9 | MESI sharing costs and what each memory model guarantees. | |
2 | 9 | Counters, top-down triage, roofline bounds, and tuning moves. | |
1 | 6 | When accelerators win, dataflow contracts, locality, and integration. | |
2 | 9 | PPA budgets, power and energy, floorplans, and signoff gates. | |
2 | 14 | Whiteboard method, worked scenarios, and a deduplicated Q and A bank. |
Interview in two weeks
Days | Focus | Exit check |
|---|---|---|
1-2 | Derive CPI from a stall breakdown. | |
3-5 | Size a cache level with AMAT and MPKI. | |
6-8 | Place a kernel on its roofline. | |
9-11 | Trace a sharing miss to its traffic. | |
12-14 | Interview Method and Worked Scenarios, Architecture Interview Q and A Bank | Close a whiteboard answer with numbers. |
Practitioner in six weeks
Week | Focus | Exit check |
|---|---|---|
1 | Pipeline Throughput, Branch Prediction and Fetch, Out-of-Order Superscalar Execution | Attribute an IPC gap to frontend, backend, or memory. |
2 | Caches, Memory Bandwidth and Latency, Virtual Memory and the TLB | Triage a miss storm by capacity, conflict, or translation. |
3 | On-Chip Networks, Cache Coherence for the Architect, Memory Ordering Models | Separate fabric stalls from sharing costs. |
4 | Run one-experiment triage on a live workload. | |
5 | Accelerators for the Architect, PPA at System Level, Power and Energy for the Architect | Defend an offload and its budget impact. |
6 | Interview Method and Worked Scenarios, Architecture Interview Q and A Bank | Present a full metric to validation story. |
How to use this course
For each topic, write one line naming the workload, the metric, the mechanism, the cheapest experiment, and the validation. That order is the whole method: metric, mechanism, experiment, change, validation.
Check yourself A workload slows down after a layout change. What is your first sentence?
Name the workload and the moved metric, then the suspect mechanism. Performance Method builds the full triage.