Lesson Notes By Weeks and Term v5 - Grade 11

Lesson Video

This page supports the lesson note with a companion video and a short classroom-ready summary.

For class groups and homework, share this lesson page so learners also get the summary, objectives, and full lesson context.

Performance objectives

• Identify common system performance bottlenecks (CPU, RAM, etc.).
• Use system monitoring tools like Task Manager.
• Apply basic troubleshooting techniques.
• Differentiate between hardware and software issues.
• Understand the importance of documenting solutions.

Lesson summary

This week, we delve into the critical aspects of system technologies: performance monitoring and effective troubleshooting. In our increasingly digital world, understanding how computer systems work, how to identify problems, and how to resolve them is not just a technical skill – it’s a fundamental life skill. Whether you are using a computer for schoolwork, entertainment, or running a small business from home, knowing how to maintain and fix your system will save you time, money, and frustration. From slow internet speeds affecting your online learning to a malfunctioning printer hindering your project submission, these skills directly impact your ability to succeed.

Lesson notes

2.1 System Performance Bottlenecks A system bottleneck occurs when a component limits the overall performance of the entire system.

Think of it like a traffic jam: even if the rest of the road is clear, the jam slows everyone down.

Common bottlenecks include: CPU Usage: The Central Processing Unit (CPU) is the brain of the computer. High CPU usage (close to 100%) indicates that the CPU is struggling to keep up with the demands placed on it. This can be caused by running too many programs simultaneously, resource-intensive applications (like video editing or gaming), or malware.

Why it Matters: A maxed-out CPU leads to slow response times, program crashes, and overall system instability.

How to Identify: Use Task Manager (Windows), Activity Monitor (macOS), or `top`/`htop` (Linux) to monitor CPU usage.

Memory Usage (RAM): Random Access Memory (RAM) is where the computer stores data that it is actively using. If the system runs out of RAM, it starts using the hard drive as "virtual memory," which is much slower.

Why it Matters: Insufficient RAM results in sluggish performance as the system constantly swaps data between RAM and the hard drive.

How to Identify: Monitor RAM usage using the same tools mentioned above. Look for high memory utilization (e.g., above 80%) and frequent disk activity (page file usage).

Disk I/O (Input/Output): Disk I/O refers to the rate at which data is being read from or written to the hard drive (or SSD). Slow disk I/O can be a bottleneck if applications are frequently accessing data on the disk.

Why it Matters: Slow disk I/O particularly affects applications that rely heavily on reading and writing data, such as databases or video editing software.

How to Identify: Task Manager/Activity Monitor can display disk I/O activity. Use tools like `iostat` (Linux) for more detailed analysis.

Network Congestion: If the computer is connected to a network, network congestion can become a bottleneck. This occurs when the network is overloaded with traffic, leading to slow data transfer speeds.

Why it Matters: Network congestion affects online activities like browsing the internet, streaming videos, and downloading files.

How to Identify: Use network monitoring tools (like `ping` or `traceroute` in the command line) to check network latency and packet loss. Also, consider the number of devices sharing the same network. A household with multiple users streaming videos simultaneously will likely experience congestion. 2.2 System Monitoring Tools Windows Task Manager: Accessed by pressing Ctrl+Shift+Esc. It provides real-time information about CPU usage, memory usage, disk I/O, network activity, and running processes. macOS Activity Monitor: Found in the Utilities folder within Applications. Similar to Task Manager, it offers comprehensive performance monitoring. Linux `top` and `htop`: Command-line tools that display real-time system information, including CPU usage, memory usage, and running processes. `htop` is an enhanced version of `top` with a more user-friendly interface. Install `htop` using `sudo apt install htop` (Debian/Ubuntu) or `sudo yum install htop` (CentOS/RHEL). 2.3 Basic Troubleshooting Techniques Restarting: Often, a simple restart can resolve temporary glitches. Close all programs and restart the computer.

Updating Drivers: Outdated drivers can cause compatibility issues and performance problems. Update drivers for graphics cards, network adapters, and other hardware components.

Checking Hardware Connections: Ensure that all cables (power, network, USB) are securely connected.

Closing Unnecessary Programs: Close any programs that are not currently in use to free up system resources.

Running Antivirus Scan: Malware can significantly impact system performance. Run a full system scan with a reputable antivirus program.

Disk Defragmentation (Windows): Defragmenting the hard drive reorganizes files, which can improve performance.

Note: This is not necessary for SSDs.

Disk Cleanup: Remove temporary files, cached data, and other unnecessary files to free up disk space.

Checking Event Logs: Both Windows and Linux keep logs of system events, including errors and warnings. Reviewing these logs can help identify the cause of problems. In Windows, use the Event Viewer. In Linux, logs are typically stored in `/var/log`. 2.4 Hardware vs.

Software Issues Hardware Issues: Problems related to physical components of the computer (e.g., faulty hard drive, failing RAM, overheating CPU).

Software Issues: Problems related to the operating system, applications, drivers, or malware. Differentiating between Hardware and Software: BSOD (Blue Screen of Death): Can indicate either a hardware or software problem. Repeated BSODs often point to hardware.

Application Crashes: More likely a software issue (e.g., a bug in the application).

Device Not Recognized: Usually a driver issue (software) or a faulty connection (hardware).