Blame

d190aa cloudy-jc 2026-04-12 14:01:32
Add GPU vs CPU wiki page with YouTube embed
1
# GPU vs CPU
2
f09b43 cloudy-jc 2026-04-19 16:09:46
Wiki: convert all wikilinks to Markdown links — fix subdir routing OtterWiki interpreted [[dt7/Page|Display]] by using the Display text as the link target (404 because no page exists at that name). Converted all 54 wikilinks in dt7/, sd/, and Home.md to Markdown [Display](/path) syntax, which OtterWiki resolves correctly. Affected: every Y7 leaf page footer's Hub backlink, every cross-link between Y7 pages, both hub pages' page lists, and the Home.md lobby. No content changes — only link syntax + URL encoding. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3
*A companion page to [Workshop 1 Hardware and Networks](/dt7/Workshop%201%20Hardware%20and%20Networks).*
d190aa cloudy-jc 2026-04-12 14:01:32
Add GPU vs CPU wiki page with YouTube embed
4
5
When you cracked open a laptop in Workshop 1, you spotted the CPU — the brain of the computer. It fetches instructions, does the maths, and keeps everything running. A modern CPU has a handful of very fast, very clever cores (usually 4 to 16). It can juggle lots of different jobs, but it tackles them roughly one at a time per core.
6
7
The GPU sits on a separate chip, often right next to the CPU. It was originally built to push pixels onto your screen — millions of tiny colour calculations every frame. To do that, it doesn't need a few brilliant cores; it needs **thousands of simple ones** all working at once. Each individual core is slower than a CPU core, but when thousands fire together the total throughput is enormous.
8
9
Here's an analogy: imagine you need to deliver 1 000 parcels across town. A CPU is like one very fast truck — it zooms between addresses, but it still visits them one by one. A GPU is like 1 000 cyclists who each grab a parcel and pedal off at the same time. No single cyclist is as fast as the truck, but the whole fleet finishes the job far sooner.
10
11
This is exactly why AI researchers love GPUs. Training an AI model means doing millions of simple maths operations (multiply, add, multiply, add — over and over). A CPU would grind through them in a long queue. A GPU spreads them across thousands of cores and finishes in a fraction of the time.
12
13
You've already seen the CPU inside a laptop. The GPU sits right next to it — and after watching the video below, you'll never forget what makes them different.
14
15
---
16
17
## The Video
18
19
{{Video|src=https://www.youtube.com/watch?v=8_ZTvG1WQxM}}
20
21
In this clip, the *Mythbusters* team up with NVIDIA to demonstrate the difference using paintball guns. One gun fires one ball at a time (the CPU). A massive wall of guns fires thousands at once (the GPU). The result: the Mona Lisa, painted in about 80 milliseconds.
22
23
---
24
25
## What to Watch For
26
27
- **The single-gun pass vs the wall of guns** — notice how the single gun is accurate but painfully slow, while the wall completes the whole image almost instantly. That's the core trade-off: few fast cores vs many parallel ones.
28
- **How the final image comes together** — the GPU rig doesn't paint one row at a time. Every part of the picture appears at once. That's parallelism in action.
29
- **The size of the rig** — look at how many barrels are in the GPU wall. A real GPU has even more cores than that (modern ones have over 10 000).
30
- **Why accuracy per core matters less** — each paintball lands roughly where it should, not perfectly. GPUs work the same way: individually simple, collectively powerful.
31
32
---
33
a917ab cloudy-jc 2026-04-13 09:44:20
Add icons and visual flair to Have a Go section of GPU vs CPU page Font Awesome icons, callout blocks, numbered circles, and a hint box make the section stand out for Year 7 students. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
34
## <i class="fas fa-lightbulb"></i> Have a Go
1e5978 cloudy-jc 2026-04-12 16:06:49
Add 'Have a Go' learning task to GPU vs CPU page Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
35
a917ab cloudy-jc 2026-04-13 09:44:20
Add icons and visual flair to Have a Go section of GPU vs CPU page Font Awesome icons, callout blocks, numbered circles, and a hint box make the section stand out for Year 7 students. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
36
::: info
37
**<i class="fas fa-pencil-alt"></i> Your turn!** Grab a pen (or a keyboard) and have a crack at these.
38
:::
39
a7bfed cloudy-jc 2026-04-14 11:43:45
Fix literal &mdash; entities showing as text instead of em dashes Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
40
**<i class="fas fa-film"></i> Question** ① — In the video, the CPU side uses one paintball gun and the GPU side uses a massive wall of them. Why does the GPU wall finish the picture so much faster, even though each individual paintball is no more accurate than the single gun's shot?
a917ab cloudy-jc 2026-04-13 09:44:20
Add icons and visual flair to Have a Go section of GPU vs CPU page Font Awesome icons, callout blocks, numbered circles, and a hint box make the section stand out for Year 7 students. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
41
a7bfed cloudy-jc 2026-04-14 11:43:45
Fix literal &mdash; entities showing as text instead of em dashes Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
42
**<i class="fas fa-microchip"></i> Question** ② — Imagine you're designing a computer that needs to train an AI model *and* run a web browser at the same time. Which chip handles which job, and why?
a917ab cloudy-jc 2026-04-13 09:44:20
Add icons and visual flair to Have a Go section of GPU vs CPU page Font Awesome icons, callout blocks, numbered circles, and a hint box make the section stand out for Year 7 students. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
43
44
::: tip
a7bfed cloudy-jc 2026-04-14 11:43:45
Fix literal &mdash; entities showing as text instead of em dashes Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
45
⚡ **Hint:** Think about the truck vs cyclists analogy from above — which tasks need speed, and which need scale?
a917ab cloudy-jc 2026-04-13 09:44:20
Add icons and visual flair to Have a Go section of GPU vs CPU page Font Awesome icons, callout blocks, numbered circles, and a hint box make the section stand out for Year 7 students. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
46
:::
1e5978 cloudy-jc 2026-04-12 16:06:49
Add 'Have a Go' learning task to GPU vs CPU page Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
47
48
---
49
f09b43 cloudy-jc 2026-04-19 16:09:46
Wiki: convert all wikilinks to Markdown links — fix subdir routing OtterWiki interpreted [[dt7/Page|Display]] by using the Display text as the link target (404 because no page exists at that name). Converted all 54 wikilinks in dt7/, sd/, and Home.md to Markdown [Display](/path) syntax, which OtterWiki resolves correctly. Affected: every Y7 leaf page footer's Hub backlink, every cross-link between Y7 pages, both hub pages' page lists, and the Home.md lobby. No content changes — only link syntax + URL encoding. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
50
See also: [Workshop 1 Hardware and Networks](/dt7/Workshop%201%20Hardware%20and%20Networks)
d190aa cloudy-jc 2026-04-12 14:01:32
Add GPU vs CPU wiki page with YouTube embed
51
52
*Last updated: April 2026.*
ce5b8c cloudy-jc 2026-04-19 16:06:03
Wiki: reorganise into dt7/ and sd/ subdirs (per-course namespaces) Moves all current pages into per-course subdirectories so each cohort gets a clean namespace with its own URL prefix and natural sidebar grouping: dt7/ Year 7 Digital Technologies (9 pages + 2 attachment folders) sd/ VCE Software Development (was SAT/, with C01 + Resources) New top-level structure: Home.md ← lobby (2 doors) dt7/Year 7 Hub.md ← Y7 cohort landing sd/VCE Software Development Hub.md ← VCE cohort landing dt7/* and dt7/<page>/ ← Y7 pages + attachments sd/* and sd/C01/ ← VCE pages + attachments Link rewrites: - All [[Page]] cross-links qualified to [[dt7/Page]] for the moved Y7 pages - All image refs /<page>/img.png updated to /dt7/<page>/img.png - Every Y7 leaf page now ends with "← Back to [[dt7/Year 7 Hub]]" Home.md rewritten as a minimal lobby with 2 entries; the per-cohort hubs do all the curation work. Why dt7/ + sd/: Jeremy expects more courses (Y8, Y9, etc). Subdir layout scales; OtterWiki sidebar will auto-group by directory tree. Cost: 5 way2.cc shortlinks (ca2-ca6) need their target URLs updated to /dt7/<page> paths. Following commit handles that via the way2.cc admin API. ca7-caa point at YouTube directly and don't need touching. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
53
54
f09b43 cloudy-jc 2026-04-19 16:09:46
Wiki: convert all wikilinks to Markdown links — fix subdir routing OtterWiki interpreted [[dt7/Page|Display]] by using the Display text as the link target (404 because no page exists at that name). Converted all 54 wikilinks in dt7/, sd/, and Home.md to Markdown [Display](/path) syntax, which OtterWiki resolves correctly. Affected: every Y7 leaf page footer's Hub backlink, every cross-link between Y7 pages, both hub pages' page lists, and the Home.md lobby. No content changes — only link syntax + URL encoding. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
55
← Back to [Year 7 Hub](/dt7/Year%207%20Hub)