top and htop (live monitoring) in Linux CLI - Time & Space Complexity

Time Complexity: top and htop (live monitoring)

O(n log n)

Understanding Time Complexity

When using live monitoring tools like top and htop, it's important to understand how their performance changes as the system load grows.

We want to know how the cost of updating the display scales with the number of running processes.

Scenario Under Consideration

Analyze the time complexity of the following simplified command loop from top or htop:

while true; do
  ps -eo pid,comm,pcpu,pmem --sort=-pcpu | head -n 20
  sleep 1
done

This loop fetches and displays the top 20 CPU-consuming processes every second.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Listing all processes and sorting them by CPU usage.
• How many times: This happens once every second, repeatedly.

How Execution Grows With Input

As the number of running processes increases, the system must sort more items before showing the top 20.

Input Size (n)	Approx. Operations
10	Sorting 10 processes
100	Sorting 100 processes
1000	Sorting 1000 processes

Pattern observation: The sorting work grows as the number of processes grows, making updates slower with more processes.

Final Time Complexity

Time Complexity: O(n log n)

This means the time to update the display grows a bit faster than the number of processes because sorting takes more work as the list grows.

Common Mistake

[X] Wrong: "The update time stays the same no matter how many processes run."

[OK] Correct: Sorting all processes takes more time as the list grows, so updates slow down with more processes.

Interview Connect

Understanding how live monitoring tools scale helps you think about performance in real systems, a useful skill for many tech roles.

Self-Check

What if the tool only scanned the top 20 processes without sorting all? How would the time complexity change?

Practice

1. What is the main purpose of the top command in Linux?

easy

A. To display live system and process information

B. To edit text files

C. To compile programs

D. To manage user accounts

Solution

1. Step 1: Understand the function of top

   The top command shows real-time information about system processes and resource usage.

2. Step 2: Compare with other options

   Options B, C, and D relate to different commands or tools, not top.

3. Final Answer:

   To display live system and process information -> Option A

4. Quick Check:

   top = live system info [OK]

Hint: Remember: top shows live system stats [OK]

Common Mistakes:

• Confusing top with text editors like nano
• Thinking top manages users
• Assuming top compiles code

2. Which of the following commands correctly starts htop in the terminal?

easy

A. start htop

B. htop -start

C. htop &

D. run htop

Solution

1. Step 1: Identify correct syntax to run htop

   The command htop runs the program; adding & runs it in background.

2. Step 2: Check other options for correctness

   Options B, C, and D are not valid Linux commands to start htop.

3. Final Answer:

   htop & -> Option C

4. Quick Check:

   Run htop with 'htop &' [OK]

Hint: Run htop by typing 'htop' or 'htop &' [OK]

Common Mistakes:

• Using invalid flags like -start
• Typing 'start htop' which is Windows style
• Using 'run htop' which is not a Linux command

3. You run top and see a process using 95% CPU. What does this indicate?

medium

A. The process is waiting for user input

B. The process is sleeping and not active

C. The process is stopped

D. The process is using most of the CPU power

Solution

1. Step 1: Interpret CPU usage in top

   High CPU percentage means the process is actively using CPU resources.

2. Step 2: Understand other states

   Sleeping or waiting processes use little CPU; stopped processes do not use CPU.

3. Final Answer:

   The process is using most of the CPU power -> Option D

4. Quick Check:

   High CPU% = active process [OK]

Hint: High CPU% means active process using CPU [OK]

Common Mistakes:

• Thinking high CPU means sleeping
• Confusing waiting with stopped
• Assuming stopped processes use CPU

4. You try to run htop but get: command not found. What should you do?

medium

A. Restart the computer

B. Install htop using the package manager

C. Run top instead

D. Check if you typed htop correctly

Solution

1. Step 1: Understand 'command not found' error

   This means htop is not installed or not in PATH.

2. Step 2: Fix by installing htop

   Use package manager like sudo apt install htop or sudo yum install htop to install.

3. Final Answer:

   Install htop using the package manager -> Option B

4. Quick Check:

   command not found = install missing tool [OK]

Hint: Install missing commands with package manager [OK]

Common Mistakes:

• Restarting without installing
• Ignoring the error and running top
• Not checking spelling before install

5. You want to find and kill the process using the most memory using htop. What steps should you follow?

hard

A. Sort by memory, select process, press F9 to kill

B. Sort by CPU, select process, press F10 to kill

C. Sort by PID, select process, press F3 to kill

D. Sort by user, select process, press F5 to kill

Solution

1. Step 1: Sort processes by memory usage in htop

   Press F6 or click the memory column to sort descending by memory.

2. Step 2: Select the top memory-consuming process and kill it

   Use arrow keys to select process, then press F9 to kill it.

3. Final Answer:

   Sort by memory, select process, press F9 to kill -> Option A

4. Quick Check:

   htop kill = sort mem + F9 [OK]

Hint: In htop, F9 kills selected process after sorting [OK]

Common Mistakes:

• Using wrong function keys to kill
• Sorting by CPU instead of memory
• Trying to kill by PID without selecting