CPU Performance

💻 Computer Science Years 9–11 Foundation

How clock speed, number of cores and cache size each affect how fast a CPU gets work done.

Open this lesson, with practice and a printable worksheet →

Two laptops sit side by side. One opens a game in three seconds; the other takes twenty. Same job, wildly different speed — and the difference lives in the CPU. But "faster CPU" isn't one number. Performance comes from three things working together: clock speed, the number of cores, and the size of the cache.

Why this matters: When you buy or build a computer, the marketing throws numbers at you — 3.5 GHz, quad-core, 8 MB cache. Knowing what each one actually does stops you overpaying for a spec that won't help what you do.
Core 1Core 2 Core 3Core 4 cache
Four cores sharing a fast central cache.

Clock speed — how fast the beat is

slow clockfast clockeach rise = one cyclemore ticks per second
Higher clock speed = more ticks per second = more cycles pushed through.

The CPU works to a steady beat called the clock, measured in hertz (cycles per second). A speed of 3.5 GHz means 3.5 billion beats every second, and each beat can push the fetch–decode–execute cycle along. Picture a drummer setting the pace for rowers: a faster drum means more strokes per minute. All else being equal, a higher clock speed means more instructions per second.

Cores — how many workers

A core is a complete processing unit. A dual-core chip has two, a quad-core has four. More cores means the CPU can genuinely do more than one thing at the same time — like opening more checkout tills in a busy shop. But there's a catch: the task has to be split up to benefit. Some jobs can't be shared, so a second core sits idle.

Cache — how close the tools are

CPUCacheRAMfastslowa hit in cache avoids the slow trip to RAM
Cache keeps hot data close, so the CPU rarely makes the slow trip to RAM.

Cache is a small amount of very fast memory built into the CPU. It keeps copies of the data and instructions the CPU uses most, so it doesn't have to keep reaching out to slower main memory (RAM). It's a chef keeping salt and oil on the worktop rather than walking to the store cupboard each time. Bigger, well-used cache = fewer slow trips = faster work.

FactorWhat it measuresRough effect of increasing it
Clock speedCycles per second (GHz)More instructions per second
Number of coresIndependent processing unitsMore tasks in parallel
Cache sizeFast on-chip memoryFewer slow trips to RAM
Worked example: A CPU runs at 2 GHz. How many clock cycles is that per second? — 2 GHz = 2 × 1,000,000,000 = 2 billion cycles per second. If it were upgraded to 4 GHz, it would tick twice as often each second.
2bn2 GHz4bn4 GHz
Double the GHz, double the cycles each second (2bn → 4bn).
Common mistake: A higher clock speed does not always mean a faster computer. A quad-core at 3 GHz can beat a dual-core at 4 GHz on tasks that split across cores — and a tiny cache can bottleneck even a fast core.

Tip: judge a CPU by all three together — speed of the beat, number of workers, and how close the tools are. No single number tells the whole story.

Get the printable worksheet →
← Inside the CPU → Memory
← Sasta Basta home All subjects