Unlock Linux Performance: Master the ‘time’ Command and Its Hidden Features

1. Basic Usage

The time command measures how long a program runs. A typical example shows the real (wall‑clock) time, user CPU time, and system CPU time:

root@chopin:~$ time find . -name "chopin.txt"
......
real   0m0.174s
user   0m0.084s
sys    0m0.084s

Here real is the elapsed wall‑clock time, user is CPU time spent in user mode, and sys is CPU time spent in kernel mode.

real : total elapsed time from start to finish.

user : CPU time consumed while executing user‑space code.

sys : CPU time consumed by kernel‑space operations.

Because user + sys excludes time the process spends blocked on I/O or waiting for scheduling, real can be larger than the sum of user and sys . For example:

root@chopin:~$ time sleep 2
real   0m2.001s
user   0m0.000s
sys    0m0.000s

Here the program does almost no CPU work, so the real time equals the sleep duration.

2. Which time Are You Using?

Linux may provide three different implementations:

# 1. Bash
time is a shell keyword
# 2. Zsh
time is a reserved word
# 3. GNU time
time is /usr/bin/time

Running type time reveals that the current shell (Bash) uses the built‑in keyword. The GNU version, located at /usr/bin/time, offers richer functionality and is the focus of the advanced sections.

3. Powerful GNU time Features

GNU time can provide more detailed statistics, custom output formats, and the ability to write results to a file.

Simple usage with absolute path:

/usr/bin/time sleep 2
0.00user 0.00system 0:02.00elapsed 0%CPU (0avgtext+0avgdata 1784maxresident)k
0inputs+0outputs (0major+72minor)pagefaults 0swaps

Preserve the shell‑style output using -p:

/usr/bin/time -p sleep 2
real 2.00
user 0.00
sys  0.00

Show verbose information with -v:

/usr/bin/time -v sleep 2
Command being timed: "sleep 2"
User time (seconds): 0.00
System time (seconds): 0.00
Percent of CPU this job got: 0%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:02.00
... (additional memory, I/O, and context‑switch stats)
Exit status: 0

Write the statistics to a file with -o (append with -a):

/usr/bin/time -v -o a.txt sleep 2

Define a custom format using -f:

/usr/bin/time -f "real %e
user %U
sys %S" sleep 1
real 1.00
user 0.00
sys  0.00

Below are the tables of format specifiers (image omitted for brevity).

4. Using the Metrics for Performance Analysis

The three time values help identify program characteristics:

If user + sys ≥ real , the program is CPU‑bound (compute‑intensive).

If user + sys ≪ real , the program spends significant time waiting for I/O or blocked on scheduling.

Additional metrics such as context switches and page‑fault counts (shown in the verbose output) reveal further performance bottlenecks. Excessive context switches indicate frequent kernel‑mode interruptions, while a high number of major page faults suggests poor memory locality.

Tip: In Linux, user mode code runs with limited privileges, while kernel mode has full access to hardware resources. Understanding the distinction clarifies why user and sys times exclude I/O wait and scheduling delays.

By interpreting these statistics, developers can decide whether to optimise CPU usage, reduce I/O latency, or address memory‑access patterns.