Feynman
← All modules
CS80EHow Computing WorksAdvanced60 min

Modern Computer Architecture

Why chips got fast (pipelines, caches, and parallelism) and why your code's speed depends on the silicon.

AI tutor is turned off for this class

Use the CS80E lectures, notes, and assignments below to keep learning.

Big Idea

How Computing Works

Grade bands

K-2 · 3-5 · 6-8 · 9-12

AI literacy pillar

How AI works · Ethics

View on the ladder →

Lesson overview

Why chips got fast (pipelines, caches, and parallelism) and why your code's speed depends on the silicon. This module climbs from an everyday intuition to the real mechanism, then names the Stanford course it descends from.

Teacher script · ~45 min

  1. 0–5

    Hook

    A processor doesn't do one whole instruction then the next; like a car factory, it splits work into stages and keeps all stages busy on different instructions at once. This 'pipelining' is a big reason chips feel fast: many things half-done simultaneously beats one thing done fully at a time.

  2. 5–15

    Explore

    Students do the activity in pairs: Cook from a recipe keeping the 5 ingredients you use most on the counter, the rest in the pantry. Fewer pantry trips = faster. That's caching.

  3. 15–30

    Explain

    Clock speeds stopped climbing, so chips went wide: multiple cores, vector units doing one operation on many numbers at once, and GPUs with thousands of tiny cores. Modern speed comes from parallelism, which is exactly why training neural nets lives on GPUs. The catch: not all work splits cleanly.

  4. 30–40

    Connect to the summit

    Show students this is the real thing professionals build: CS80E / architecture, the real thing. Why chips got fast (pipelines, caches, and parallelism) and why your code's speed depends on the silicon.

  5. 40–45

    Check

    Run the formative check below. Anyone who can explain a key term in their own words has it.

Student activity

Cook from a recipe keeping the 5 ingredients you use most on the counter, the rest in the pantry. Fewer pantry trips = faster. That's caching.

Slides

1Title: Modern Computer Architecture
2Hook: A chip is an assembly line
3Do it: Keep what you'll need nearby
4How it works: Doing many things at once
5Key idea: Pipelining
6Key idea: Cache
7Key idea: Memory hierarchy
8From the summit: CS80E at Stanford

Formative check

  • 1.In your own words, what is "Pipelining"? (Looking for: Overlapping the stages of many instructions like an assembly line.)
  • 2.In your own words, what is "Cache"? (Looking for: A small, very fast memory holding recently-used data near the processor.)
  • 3.In your own words, what is "Memory hierarchy"? (Looking for: Layers of storage trading speed for size, from registers to disk.)

Carry-away concepts

Pipelining
Overlapping the stages of many instructions like an assembly line.
Cache
A small, very fast memory holding recently-used data near the processor.
Memory hierarchy
Layers of storage trading speed for size, from registers to disk.
Parallelism
Doing many computations simultaneously across cores or units.

From the summit · the Stanford source

You learn how processors execute instructions efficiently: pipelining, memory hierarchy, caching, and parallelism.

This module descends from CS80E at Stanford. Students who climb the full ladder arrive here.