Skip to content
digiwleeaTools
LearnGlossaryAboutCheat sheetHow a CPU worksBuild a CPUToolsOpen the lab →

Reading Computer Architecture: A Quantitative Approach? Build the basics

Computer Architecture: A Quantitative Approach, by John L. Hennessy and David A. Patterson, with Christos Kozyrakis joining for the 7th edition (Morgan Kaufmann, 2025), is the advanced book on designing fast processors and systems. Its chapters are Fundamentals of Quantitative Design and Analysis; Memory Hierarchy Design; Instruction-Level Parallelism and Its Exploitation; Data-Level Parallelism in Vector, SIMD, and GPU Architectures; Thread-Level Parallelism; Warehouse-Scale Systems for Utility Computing; and Domain-Specific Architectures. Printed appendices review Instruction Set Principles, the Memory Hierarchy and Pipelining, and online appendices cover topics such as Computer Arithmetic. The chapters build on hardware the appendices only review. This page points to live circuits for that groundwork.

What the book does best

It teaches architecture as engineering with numbers: every design choice is weighed by its measured effect on performance, power and cost, from caches and branch prediction to GPUs, warehouse-scale computers and domain-specific accelerators. It is widely used in advanced computer architecture courses. (digiwleea is an independent project, not affiliated with Morgan Kaufmann, Elsevier or the authors.)

Where digiwleea fits

digiwleea works at the other end of the stack: in the browser you build gates from CMOS transistors, then adders, registers, memory and control, up to a small 8-bit CPU, with every part checked against its truth table. That makes it a place to get a feel for the circuits the book takes as given (a cache's tag compare, a pipeline register, a carry-lookahead adder) rather than a substitute for its quantitative chapters. Chapters 4 to 7 (vector and GPU, thread-level parallelism, warehouse-scale and domain-specific systems) have no counterpart here.

Computer Architecture: A Quantitative Approachdigiwleea
LevelAdvanced, quantitative design of fast processors and systemsIntroductory, from transistors to a small CPU
TopicsMemory hierarchy, ILP, GPUs, multicores, warehouse-scale, acceleratorsGates, arithmetic, memory, control, a basic CPU
MethodPerformance models and measurementsCircuits you build and simulate live
PricePaid textbookFree lab and Act I; Premium for the full course

The groundwork, live

Titles are the 7th edition's; next to each, the digiwleea lessons and live circuits on the same basics:

Starting out? The introductory books by the same authors and others have chapter-by-chapter companions here: Computer Organization and Design, Digital Design and Computer Architecture and Structured Computer Organization.

No sign-up is needed to start: open the lab and place your first transistor, or read the free theory course. The account (and the AI tutor) are optional.

More comparisons: Books, courses and projects

See for yourself: build a logic gate from transistors in the simulator, then follow the path from sand to an 8-bit CPU.

Open the digiwleea lab →

Frequently asked

What is the difference between Computer Architecture: A Quantitative Approach and Computer Organization and Design?

Both are by Hennessy and Patterson. Computer Organization and Design is the introductory book on how a computer works; Computer Architecture: A Quantitative Approach is the advanced book on designing fast processors and systems, and it reviews the basics only in its appendices.

What are the chapters of Computer Architecture: A Quantitative Approach?

In the 7th edition: Fundamentals of Quantitative Design and Analysis; Memory Hierarchy Design; Instruction-Level Parallelism and Its Exploitation; Data-Level Parallelism in Vector, SIMD, and GPU Architectures; Thread-Level Parallelism; Warehouse-Scale Systems for Utility Computing; Domain-Specific Architectures; plus appendices on instruction sets, memory hierarchy, pipelining and more.

Do I need to know digital logic before reading it?

It helps to know how caches, pipelines and arithmetic circuits work, since the chapters assume them. Building them once, for example as live circuits in a browser lab, makes the quantitative arguments much easier to follow.