Grade 10 introduced the CPU and motherboard as components. Grade 11 asks how they actually talk to each other and what makes one CPU faster than another.
CPU design โ techniques used to increase how much work a CPU can do per second:
Registers, ALU and CU (recap from Grade 10, now with more depth):
Performance concepts:
Caching โ keeping frequently-used data closer to where it's needed to reduce latency:
| Cache type | Purpose |
|---|---|
| Processor cache (L1/L2/L3) | Stores recently/frequently used data and instructions right next to the CPU cores |
| Disk cache | A portion of RAM (or a drive's own memory) used to speed up repeated reads/writes to secondary storage |
| Browser cache | Stores website files (images, scripts) locally so a page loads faster on a repeat visit |
| Proxy/web cache | A shared cache (often on a network) that stores web content so multiple users don't need to re-download the same content |
Motherboard function and connecting components:
Example
Why does a 3.5GHz quad-core CPU sometimes feel slower than a 3.0GHz CPU with a bigger cache? Because clock speed alone doesn't determine performance โ cache size reduces how often the CPU has to wait (high latency) for slower RAM, so a well-cached CPU can outperform a nominally 'faster' one on real workloads.
๐ก Exam Tip
When asked to 'discuss how components interact', always mention the bus system explicitly โ most students only describe the CPU and RAM, but the marks are often in explaining how data physically travels between them.