Skip to main content
EnglandComputer ScienceSyllabus dot point

What are the processor's components, and how does the fetch-execute cycle work?

Understand the components of the processor (ALU, control unit, registers), the fetch-decode-execute cycle, the role of each register, and the factors affecting processor performance.

A focused answer to AQA A-Level Computer Science 4.7.3, covering the components of the processor (ALU, control unit, registers), the fetch-decode-execute cycle, the role of each register, and the factors affecting processor performance.

Generated by Claude Opus 4.89 min answer

Reviewed by: AI editorial process; not yet individually human-reviewed

Have a quick question? Jump to the Q&A page

Jump to a section
  1. What this dot point is asking
  2. Components of the processor
  3. The fetch-decode-execute cycle
  4. Factors affecting performance

What this dot point is asking

AQA wants you to name the components of the processor and the special registers, describe the fetch-decode-execute cycle step by step, and explain the factors that affect processor performance.

Components of the processor

Registers are the fastest storage in the machine because they sit inside the processor itself, which is why the cycle works through them rather than through main memory at every step. Each special register has a single, well-defined job, and many exam errors come from swapping their roles, so it is worth memorising precisely what each one holds.

The fetch-decode-execute cycle

This cycle is the concrete realisation of the stored program concept: because instructions live in memory, the processor simply fetches whatever is at the program counter, runs it, and advances. A jump or branch instruction works by changing the program counter during execution, which is how loops and selection in a high-level program ultimately translate into machine behaviour. Every program your computer runs is this same loop repeated billions of times per second.

Factors affecting performance

These factors interact, which is why raw clock speed alone does not determine real performance. A fast processor starved of data by a small cache or a narrow bus will stall, and extra cores help only tasks that can be split to run in parallel. Understanding that performance is a balance across these factors, rather than any single number, is what distinguishes a strong answer.

Exam-style practice questions

Practice questions written in the style of AQA exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.

AQA 20195 marksDescribe the fetch stage of the fetch-decode-execute cycle, naming the registers involved at each step and stating when the program counter is incremented.
Show worked answer →

The address of the next instruction held in the program counter (PC) is copied into the memory address register (MAR). A read signal is sent on the control bus, and the instruction at that address is fetched from main memory along the data bus into the memory data register (MDR). The instruction is then copied from the MDR into the current instruction register (CIR), ready to be decoded. At some point during the fetch the program counter is incremented so that it points to the next instruction in sequence.

Markers reward the PC to MAR transfer, the read from memory into the MDR, the copy into the CIR, and incrementing the PC (which is allowed before the instruction is decoded). Naming each register correctly is the key to full marks.

AQA 20214 marksExplain how clock speed and the number of cores each affect the performance of a processor, and explain why doubling the number of cores does not always double performance.
Show worked answer →

Clock speed is the number of cycles per second; a higher clock speed means the processor steps through the fetch-decode-execute cycle more times per second, so it executes more instructions per second. Increasing the number of cores lets the processor execute several instructions truly in parallel, raising throughput when work can be divided among the cores.

Doubling the cores does not always double performance because not all tasks can be split into independent parts that run in parallel; a task that is inherently sequential, or parts that must wait for shared data, cannot use the extra cores, so the speed-up is limited by the portion that must run serially.

Markers reward the cycles-per-second effect of clock speed, the parallelism of multiple cores, and the explanation that only parallelisable work benefits from extra cores.

Related dot points

Sources & how we know this