Linux

Linux Processes Intro — ps and top for Newcomers

Aftab Siddique

— 3 min read

Have you ever noticed your computer suddenly slowing down, fans spinning up, or a program freezing without warning? Chances are, something is running in the background that you never asked for. Before you panic or restart blindly, learning how to see what your system is actually doing can save you hours of frustration and give you real control over your machine.

Why This Matters for a Linux Beginner

In Linux, every running program, script, or system service is called a process. Unlike graphical operating systems that hide these details behind menus, Linux gives you direct visibility into exactly what is consuming your CPU and memory. For newcomers, understanding how to monitor processes builds the foundation for troubleshooting, optimizing performance, and feeling truly comfortable in the terminal. Instead of guessing why your machine feels sluggish, you will quickly identify resource-heavy applications, spot background tasks you never launched, and learn how to manage system health with confidence.

Mastering these basic tools also demystifies the command line. You will stop viewing the terminal as a scary black box and start treating it as a practical dashboard. Once you know how to read process output, everyday Linux usage becomes smoother, faster, and far less intimidating.

Step-by-Step Walkthrough

  • Grasp the core concept of a process
    Think of a process as any active task your computer is performing. Opening a web browser, playing music, or even the system managing network connections all create separate processes. Each one receives a unique identifier called a PID, which helps Linux track and manage it. Knowing this simple relationship makes reading terminal output much easier.

  • Take a quick snapshot with ps
    The ps command captures a single moment of activity. Open your terminal and run:

    ps aux
# USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
# alice      102  4.2  8.1 524320 65432 pts/0    Ss   10:15   0:03 firefox
# root       205  0.1  0.5  12340  4321 ?        Ss   09:00   0:01 systemd-logind

    Focus on the USER column to see who launched it, the PID for identification, and %CPU / %MEM to gauge resource impact. The final column shows the actual COMMAND name.

  • Switch to live monitoring with top
    While ps gives you a still photo, top provides a continuously updating dashboard. Type top and press Enter. You will immediately see a dynamic table that refreshes every few seconds. At the top, you will find system summaries like uptime and load averages. The main section lists processes sorted by default to highlight the highest resource consumers first. Use these keyboard shortcuts while inside: press P to sort by CPU usage, M to sort by memory, and q to quit when finished.

  • Filter results quickly with grep
    Sometimes you know exactly which application is causing trouble but cannot locate it in a long list. You can combine ps with the grep command to filter results instantly:

    ps aux | grep code
# alice      308 12.4 15.2 982340 124560 pts/1   Sl   10:20   0:45 code --user-data-dir
# alice      412  0.0  0.1   7234   1120 pts/1   S+   10:25   0:00 grep code

    This pipes the full process list into a text search, instantly highlighting matching lines. Note that you will also see the grep command itself in the results; this is completely normal and can be ignored.

  • Stop a problematic task safely
    If a program has frozen or is hogging resources, you can gently ask it to close using the kill command. Always start with a polite request before forcing a shutdown:

    kill 308
# If it does not close after ten seconds:
kill -9 308

    Replace 308 with the actual PID you found earlier. Use the -9 flag sparingly, as it forces immediate termination without allowing the program to save data or clean up temporary files properly.

Common Beginner Mistakes to Avoid

  • Killing critical system processes like systemd, init, or kthreadd, which can crash your session or require a full reboot
  • Confusing CPU and memory percentages, where high CPU usage is often temporary, but sustained high memory usage usually indicates a leak or unnecessary background workload
  • Running monitoring commands with sudo unnecessarily, which grants root privileges to tools that should only inspect your own user environment
  • Ignoring the COMMAND column entirely, making it difficult to distinguish between legitimate system services and unknown applications
  • Leaving top running indefinitely in terminal sessions, which can consume unnecessary resources over time

Friendly Wrap-Up

Monitoring processes does not have to be intimidating once you understand the basic tools and know exactly where to look. Start by checking ps aux when things feel slow, switch to top for real-time insights, and practice filtering output until reading process tables feels completely natural. With a little regular practice, you will quickly turn system confusion into clear, actionable knowledge. For more beginner-friendly Linux guides and hands-on troubleshooting tutorials, visit Solv-IT.

Read more