lesson 3.15.2 managing memory and processes

Using Task Manager to Monitor System Performance

Welcome back to the digital kitchen! Last time, we learned that the operating system is the ultimate manager of your computer. Today, we are putting on our detective hats to see this manager in action. Have you ever wondered what is actually happening inside your computer when you have a game, a video, and your homework open all at once? We are going to use the Task Manager to spy on the OS, just like a professional IT Support Technician does when troubleshooting a broken system!

Learning Outcomes

The Building Blocks (Factual Knowledge)

Recall the definition of a process as a program currently running in the computer's memory.

Describe the difference between primary memory and secondary storage when executing a software application.

Analyse the role of the operating system in allocating CPU time slices to different processes.

The Connections and Theories (Conceptual Knowledge)

Describe how the operating system acts as a resource manager to prevent system bottlenecks.

Analyse the impact of having insufficient RAM on the performance of multiple concurrent processes.

Evaluate why multitasking is an illusion created by rapid CPU scheduling algorithms.

The Skills and Methods (Procedural Outcomes)

Apply knowledge of system utilities to open and navigate the Task Manager or Activity Monitor.

Analyse live system data to identify which running applications are consuming the most memory and CPU resources.

Evaluate system performance by intentionally opening multiple applications and observing the live metric changes.

Digital Skill Focus: Apply diagnostic skills by using built-in operating system utility tools to actively monitor and troubleshoot system performance.

The Digital Juggling Act.

Imagine a chef in a busy kitchen. The chef is your computer's CPU (Central Processing Unit), doing all the actual cooking and calculation. The countertops where the chef places ingredients to work on right now, represent your primary memory (RAM). The big cupboards at the back where all the food is stored long-term represent your secondary storage (like your hard drive).

When you open a software application, the Operating System acts as the kitchen manager. It fetches the application from the cupboards (storage) and places it onto the countertop (RAM) so the chef (CPU) can start working on it.

But what happens if you open a game, a web browser, a music player, and a word processor all at the exact same time? The countertop gets completely full! The manager has to carefully juggle all these tasks to make sure the computer doesn't crash. We call this memory management.

Active Learning Directive
Turn these words into pictures! Draw 3 small doodles, icons, or emojis on your whiteboards that sum up the main ideas from this section. You don't need to be an artist - making it visual helps your brain remember!

The Great Balancing Act: CPU & Memory Allocation.

When you look at a system monitor, you will see a massive list of things running. To understand what is happening, we need to know the difference between an application and a process:

An application is the software program you installed (like a web browser or game).

A process is a program that is currently running in the memory. A single application might spawn several separate processes!

Because you only have one CPU (the chef) and a limited amount of RAM (the countertop), the Operating System must constantly perform a delicate balancing act to stop the computer from freezing.

First, it uses CPU scheduling. It gives the CPU to a video player for a fraction of a millisecond, then pauses it. Then it gives the CPU to the mouse for a fraction of a millisecond, then pauses it. It switches between these processes so incredibly fast that your brain thinks they are all happening at once!

Second, it controls memory allocation. It decides exactly how many megabytes of RAM each process is allowed to use.

Finally, the Operating System has to make strict priority decisions. It will always give more CPU time and memory to foreground processes (the things you are actively clicking on) and starve background processes (like a virus scan running invisibly) if the system is under heavy load.

Active Learning Directive
Boil this entire section down to exactly three bullet points. What are the absolute, unmissable facts you need to take away today?

Task The Ultimate Stress Test

Time to put on your detective hat! We are going to intentionally push your browser's mini-Operating System to its limits to see how it manages CPU priority and RAM allocation.

Get Organised!

Press Shift + Esc on your keyboard to open the Browser Task Manager.

Organise your workspace: Move the window to the side of your screen so you can see the data changing live. Make sure you can see both the

CPU

and

Memory footprint

columns.

The Baseline Test

Close all your open tabs (except this lesson page).

Find the main "Browser" process at the top of the list. What is the memory and CPU being used just to keep the browser awake? Record this in your head as your baseline.

The Stress Tests

WARNING: These tasks might break your PC!

You must run the following tests in new tabs. Watch the Task Manager carefully as you launch each one!

Test A (Low Stress): Open the Google Homepage. Notice how little RAM it takes?

Test B (Medium Stress): Open YouTube or the BBC News website and play a video. Watch the CPU spike as the video decodes.

Test C (The CPU Eater): Go to The Computing Cafe Python Tool. Copy and paste the code below, then click run. The script will pause, and then start calculating wildly! Watch the Memory and CPU columns for that tab!

import time

print("Preparing to crunch numbers...")
time.sleep(3)
print("Starting the heavy lifting...")
time.sleep(0.1)
total = 0
for i in range(1, 50000001):
  total = i * i
  if i % 1000000 == 0:
    print("Calculated " + str(i) + " loops... still going!")
    time.sleep(0.1)
print("Finished!")

Test D (The Visual CPU Stressor): Open the WebGL Aquarium. Change the number of fish to 30,000 using the drop-down menu. Watch the CPU and GPU panic!

Test E (The RAM Eaters): To test memory allocation, we need massive image files. Open Google Earth Web and spin the globe quickly. Then visit this Gigapixel Panorama online and zoom in. Watch your RAM footprint explode!

Test F (The System Crasher): Open BrowserBench and run a test. Your computer will likely freeze as the OS fails to balance the overwhelming demand! Listen to the CPU fan!!

AI Research

Need help understanding what you just witnessed? Use this exact prompt in Google AI to research the answers:

You are an expert computer science teacher. Explain to a 13-year-old why a maths script spikes the CPU but not RAM, why 3D maps use massive amounts of RAM, and what happens when a computer runs out of both. Maximum 150 words. NO intro, NO outro, NO deviation from the topic, NO follow-up questions.

The Output

Open PowerPoint or Canva and create a single presentation slide titled "The Stress Test Results". You must clearly answer these three reflection questions on your slide:

Why did the Python script cause a massive CPU spike, but barely touch the memory footprint?

Why did Google Earth and the Gigapixel Panorama use significantly more RAM than the Google Homepage?

What happens to the overall system performance when a high-priority process demands 100% of the CPU and Memory?

Outcome: You have successfully monitored resource allocation during extreme stress tests and produced a slide explaining your findings.

Today you have learnt how the operating system balances CPU time and allocates primary memory to different active processes, and how to monitor this juggling act using built-in system monitoring tools.