The specification names three factors affecting CPU performance. Each needs a reason, not just a direction.
Clock speed
The number of clock pulses per second, measured in hertz (Hz) — usually gigahertz (GHz), meaning billions of pulses per second.
Higher clock speed → more Fetch-Execute cycles completed per second → more instructions executed per second → better performance.
⚠️ But: higher clock speeds generate more heat and use more power, which limits how far speed alone can be increased.
Number of processor cores
A core is a complete processing unit — its own ALU, control unit and registers. A dual-core CPU has two, a quad-core four.
More cores → several instructions can be processed at the same time (in parallel) → more work done per second.
⚠️ But — and this is where the best marks are — software must be written to make use of multiple cores. A program that is not written for parallel processing will use only one core, so doubling the cores does not double performance. Some tasks also cannot be split up, because each step depends on the result of the previous one.
Cache size
Cache is a small amount of very fast memory inside or very close to the CPU that stores frequently used instructions and data.
Larger cache → more instructions and data can be stored close to the CPU → more requests are met from fast cache rather than slower main memory → the CPU waits less → better performance.
⚠️ But: cache is expensive per byte, so it is always far smaller than main memory, and the benefit of increasing it falls away once the data in active use already fits.
Putting them together
| Factor | Effect | Reason |
|---|
| Clock speed ↑ | Faster | More Fetch-Execute cycles per second |
| Cores ↑ | Faster (if software supports it) | Several instructions processed simultaneously |
| Cache size ↑ | Faster | More data available from fast memory, less waiting for main memory |
AQA tip. "Explain the effect" means give the mechanism. "A larger cache improves performance" scores one mark at best; "a larger cache means more frequently used instructions are stored close to the CPU, so fewer requests go to the slower main memory and the CPU spends less time waiting" scores fully.