A Practical Guide to Elementary OS System Monitor
When an elementary OS laptop feels slow, the cause is not always obvious. A web page may be using excessive processor time, a background update may be consuming storage bandwidth, or an application may have stopped responding while the rest of the desktop remains usable. System Monitor turns those impressions into measurable information about running processes, memory, CPU activity, storage and network use.
The utility is useful for everyday troubleshooting as well as deeper system administration. Its exact appearance and available tabs can vary between elementary OS releases and the version installed from AppCenter, but the main ideas remain consistent. Once you understand what each figure represents, you can distinguish a genuine resource problem from normal short-term activity and take action without randomly closing applications.
Finding Your Way Around The Monitor
You can usually open System Monitor from the Applications menu or by searching for it in the launcher. If it is not installed on your release, look for a compatible System Monitor package in AppCenter. The interface commonly includes a process list and separate resource views for CPU, memory, disks, network activity or mounted file systems. Some versions use a layout inherited from a wider Linux desktop project, while others present a more elementary-style design.
The process view is the most immediately useful screen. Each row represents a running task, although one application can appear as several processes. A browser, for example, may separate the main window, individual tabs, graphics rendering and extensions into different entries. Columns generally include the process name, user, status, CPU percentage and memory consumption. You may be able to reveal additional columns, such as process ID, priority, virtual memory or disk activity.
A process ID, or PID, is a unique number assigned while that task is running. It helps identify a specific instance when an application has opened several related processes. The user column is also important: processes belonging to your account are normally safe to manage when you know what they do, while system-owned tasks should be treated carefully. Sorting by a column is often the quickest way to find what is using the most CPU or RAM.
Do not assume that every process with an unfamiliar name is suspicious. Linux services often have technical names, and elementary OS relies on background components for notifications, networking, updates, desktop effects and hardware support. Before ending a task, select it and check the application name, window behaviour and recent activity.
Reading CPU And Memory Usage
CPU usage indicates how much processing capacity a task is using at that moment. A short burst of high usage is normal when opening a large application, exporting an image, compiling software or loading a complex website. A process that remains near the top of the list for several minutes, especially while the computer is idle, deserves closer attention. On a multi-core processor, the way percentages are displayed can differ: some monitors show one full core as 100 per cent, while others can show totals above 100 per cent.
The overall CPU graph helps put an individual process in context. If one task is consuming most of the available processing time, the slowdown may be application-specific. If all cores are busy, several programs may be competing for resources, or a legitimate job such as indexing, software updates or video encoding may be running. A fan running continuously and a warm chassis can support the evidence, but noise alone is not a diagnosis.
Memory is measured differently from storage. RAM holds data that active programs need quickly, while swap space on the drive provides slower overflow capacity when physical memory is under pressure. System Monitor may show used, available, cached and swap memory. Cached memory is not automatically a problem because Linux uses spare RAM to speed up file access and can release that cache when an application needs it.
A computer with 8 GB of RAM may feel comfortable with ordinary documents and a modest number of browser tabs, yet struggle with a video call, several web applications and an editor at the same time. This is familiar for people working from home in Brisbane or Perth, where a laptop may be handling a browser, Teams or a web meeting, music playback and an external display. Look for steadily rising swap use, sluggish switching and repeated disk activity rather than reacting to a single memory reading.
Understanding Processes And Safe Actions
A process can be running, sleeping, stopped or waiting for an event. A sleeping process is not necessarily broken; most graphical applications spend much of their time waiting for keyboard input, network data or a timer. A process marked as unresponsive is more concerning, particularly if its window cannot repaint or accept input. System Monitor may offer actions such as stop, continue, terminate and kill, with slightly different wording depending on the application version.
Stopping a process pauses it without removing it. Continuing allows a paused task to run again. Terminating asks the program to exit cleanly, giving it a chance to save data and close files. Killing is forceful and should be reserved for a program that ignores a normal termination request. Any unsaved work can be lost, and a forcefully closed application may leave behind temporary files or an incomplete operation.
Start with the least disruptive option. Save work through the application if possible, close the program normally, and only then use System Monitor if it refuses to respond. If an application has several related processes, ending the wrong one may close a window, disable an extension or leave a helper process running. Selecting the visible application rather than an unfamiliar helper is usually the safer approach.
Extra caution is needed with system processes. Ending the desktop shell, display server, session manager, network service or package-management task can log you out, interrupt a software installation or make the desktop temporarily unusable. If a process belongs to root or another service account, investigate its purpose first. The same principle applies in a workplace: monitoring and stopping another user’s task may conflict with organisational policy and the Privacy Act 1988, particularly where process names or activity could reveal personal information.
Using Resource Graphs To Diagnose Slowdowns
The resource graphs are most useful when watched over time. A sudden CPU spike followed by a return to normal may be harmless. A memory graph that climbs steadily until swap becomes active suggests a possible memory leak, an unusually demanding workload or too many open applications. A storage graph that remains busy while CPU use is low may point to file copying, indexing, an update or a program waiting on slow input and output.
Disk activity deserves special attention on older laptops fitted with mechanical hard drives. An inexpensive refurbished ThinkPad bought through the Australian second-hand market may run elementary OS reliably but still feel slow during updates because its drive has limited random-access performance. Replacing it with a solid-state drive can make a larger practical difference than adding visual tweaks. System Monitor can establish whether storage activity is the bottleneck before hardware is changed.
Network information can also prevent false conclusions. A system may appear sluggish while a large download, cloud synchronisation job or package update is using the connection. This matters in households sharing an NBN connection, particularly during evening streaming in Sydney or Melbourne. High network traffic does not necessarily mean high CPU use, and a fast local computer cannot make a congested or unstable connection respond instantly.
Use the graphs alongside what you were doing at the time. Installing a large application, importing photographs, restoring a backup and opening a browser profile can all create legitimate bursts. Note the process name, approximate duration and affected resource. Repeating the same observation after a reboot is more reliable than drawing a conclusion from one busy minute.
Keeping A Useful Troubleshooting Record
System Monitor is a diagnostic tool, not a complete performance laboratory. It may not expose every sensor, temperature reading or power statistic supported by the hardware. If battery life is poor, check the battery indicator and power settings as well as processes. A browser with many active tabs, high screen brightness and an external USB device may consume more energy than a single CPU-heavy task suggests.
For a reproducible check, begin with a normal session and wait for background startup work to settle. Record total memory, the busiest processes and whether swap is active. Then reproduce the slowdown with one change at a time. If the issue occurs during a video meeting, note the browser or meeting application, the number of open tabs and whether a camera or Bluetooth headset is connected. This is more useful than reporting simply that elementary OS is slow.
When asking for help in an elementary OS forum, share the release version, hardware model, the application involved and a short description of the pattern. A screenshot of the process list can help, but inspect it for usernames, document names, email addresses and other personal details before uploading it. Australian users should be especially mindful when troubleshooting a work computer, as device-management policies may restrict screenshots or process inspection even when the operating system itself permits it.
If a problem returns, check for application updates, system updates and known issues before changing advanced settings. Avoid downloading random “optimisation” scripts or terminating services recommended by an unverified post. elementary OS is built on familiar Linux foundations, so community advice may refer to Ubuntu or Debian tools, but commands and package versions are not always interchangeable. Confirm that instructions match your elementary OS release.
A sensible workflow is simple: observe first, identify the resource under pressure, connect it to a specific process, close the responsible application normally, and then investigate persistent causes. This approach is less risky than treating every high percentage as an emergency. It also makes decisions clearer when a laptop is being used on battery at a café, where repeated forced shutdowns can waste time and unsaved work.
System Monitor becomes most valuable when it changes your behaviour from guessing to measuring. CPU percentage reveals active computation, memory figures show whether applications are competing for RAM, storage and network graphs expose waiting, and the process list links those symptoms to real tasks. The tool cannot repair faulty hardware or poor software design, but it can show where further investigation should begin.
Open System Monitor during your next ordinary work session, sort the process list by CPU and then memory, and record the top three entries before reproducing any slowdown.
