Learn Understand first, then practice while the concept is still fresh.

M23 - Process Lab: Sluggish System

Use safe practice loads to observe a slow system, identify the cause, and restore normal behavior without guessing or overreacting.

Processes

Process Lab: Sluggish System

Use safe practice loads to observe a slow system, identify the cause, and restore normal behavior without guessing or overreacting.

30 min INTERMEDIATE BOTH Curriculum-reviewed
Prerequisites
Module M18 - Process Model: What Processes Are Module M20 - Process Management: CLI Module M22 - Performance Diagnosis
What you should be able to do after this
  • Create a harmless practice load.
  • Observe which process is causing the slowdown.
  • Stop the load cleanly and confirm the system returns to normal.

The Goal

This lab is about calm troubleshooting, not dramatic destruction.

You will create a harmless practice load, observe the system with the tools you learned, identify the responsible process, and restore normal behavior.

Safety Boundary

Only target the lab process you created yourself. Do not stop random system services or important applications while learning.

Step 1: Create a Harmless Practice Load

Create a Small CPU Load on Windows

Start-Process powershell -ArgumentList ‘-NoProfile’,‘-Command’,‘while ($true) { 1..5000 | ForEach-Object { [math]::Sqrt($_) > $null } }’ Get-Process powershell | Sort-Object CPU -Descending | Select-Object -First 5

Create a Small CPU Load on Linux

yes > /dev/null & pgrep yes

The exact load does not matter. What matters is that you know which process you created.

Step 2: Observe Before Acting

Observe the Load on Windows

Get-Process | Sort-Object CPU -Descending | Select-Object -First 10 Name, Id, CPU

Observe the Load on Linux

top

or in another shell

ps aux | grep yes

Before stopping anything, confirm:

  1. the process name
  2. the PID when relevant
  3. that it really is the source of the practice load

Step 3: Stop the Load Deliberately

Stop the Practice Process on Windows

Stop-Process -Name powershell

If that is too broad on your machine, stop by the exact process ID you observed instead.

Stop the Practice Process on Linux

pkill yes

or kill <PID>

Then re-check the process list or live view to confirm the pressure is gone.

Step 4: Reflect on the Sequence

The important part of this lab is the order:

  1. create or notice the load
  2. inspect the system
  3. identify the process
  4. stop only the right target
  5. confirm the result

That is better operational behavior than jumping straight to force.

Move On When

You are ready for the storage section when you can create a harmless process load, find it, stop it, and explain why each step happened in that order.