What "Fast" Really Means

Lesson 7 · taught by Pip

Here's the plain idea: "fast" sounds like one thing, but a computer's speed is really a few different things wearing the same word. Once you can tell them apart, the numbers on a spec sheet stop being mysterious and start being useful.

The metronome

Recall our short-order cook doing tiny steps in a row. Now imagine a metronome ticking beside them, setting the pace — on every tick, the cook may do one little step. A faster metronome means more steps per second.

A CPU has exactly such a metronome, and its speed is the clock, measured in gigahertz (GHz). One gigahertz is a billion ticks per second. So a "3.5 GHz" chip can attempt roughly three and a half billion tiny steps every second. That's the first meaning of fast: how quickly the cook can move.

Why a bigger clock isn't the whole story

Here's the catch. Two cooks can have metronomes set to the same speed, yet one finishes the meal sooner — because one gets more useful work done on each tick. A clumsy cook might need three ticks to chop an onion that a skilled one chops in a single tick. Modern chips are cleverly built to accomplish more per tick than older ones, so you genuinely cannot compare two CPUs by their gigahertz alone. A newer 3 GHz chip often beats an older 4 GHz one.

This is the most common trap people fall into: assuming the bigger number wins. Clock speed only compares fairly between very similar chips. Across different designs, it's just one clue among several.

More cooks, not a faster cook

Lesson two introduced cores — several cooks in one kitchen. Cores are a second, separate meaning of fast. More cores don't make any single dish appear quicker; they let several dishes progress at once.

This matters for some work and not others. Editing a huge video, where the job splits neatly into chunks, loves many cores — hand each cook a chunk. But some tasks are one long recipe that can't be split, and then a single fast cook beats a crowd of slower ones. So "8 cores" is great for some jobs, irrelevant for others. It depends entirely on whether the work divides.

The honest measure: benchmarks

Because clock and cores each tell only part of the story, the fairest way to compare computers is a benchmark — actually giving each machine the same real task and timing it. That sidesteps the marketing numbers and measures what you care about: how long does the thing you do actually take?

This is the grown-up version of "fast." Not a single number on a box, but: how quickly does this machine finish the work I'll really give it?

Your turn

Find your CPU's clock speed (in GHz) and its core count. Then ask yourself which of your everyday tasks are one-long-recipe jobs (writing, browsing) versus splittable ones (video, big downloads). You've just done the reasoning a spec sheet can't do for you.

🔦 But there's a hidden reason computers sometimes feel slow even with a fast chip — a giant speed gap between the parts. That's the next stop.