Understanding the Linux `time` Command: Basics, Advanced Features, and Performance Analysis

In this tutorial the author, known as "肖邦", shares a series of insights about the Linux time command, a tool commonly used to measure program execution time and compare performance of different solutions.

1. Basic usage

The simplest form runs a command and prints three values: real (wall‑clock time), user (CPU time spent in user mode) and sys (CPU time spent in kernel mode). Example:

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

The real time can be larger than the sum of user and sys because it also includes time the process spent waiting for I/O or being blocked.

Another example with sleep shows a case where user and sys are zero while real reflects the actual sleep duration:

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

On multi‑core systems the opposite can happen: user + sys may exceed real because several CPUs run in parallel.

2. Which time are you using?

Linux provides three variants:

Bash built‑in keyword

Zsh reserved word

GNU time located at /usr/bin/time

You can check the current one with type time :

root@chopin:~$ type time
time is a shell keyword

When you need the richer GNU version, invoke it with its absolute path.

3. More powerful features of GNU time

Detailed statistics

Customizable output format

Ability to write the report to a file

Examples:

Simple GNU call (full output):

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

Same format as the shell built‑in using -p :

root@chopin:~$ /usr/bin/time -p sleep 2
real 2.00
user 0.00
sys  0.00

Verbose output with -v :

root@chopin:~$ /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 statistics) ...
Exit status: 0

Write the report to a file with -o (append with -a if needed):

root@chopin:~$ /usr/bin/time -v -o a.txt sleep 2

Custom format using -f :

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

4. Role in performance analysis

The metrics reported by time map to three major resource dimensions: CPU, memory, and I/O. Understanding the relationship between real , user , and sys helps identify whether a program is CPU‑bound (user+sys ≥ real) or I/O‑bound (real » user+sys). Additional statistics such as context switches and page faults give clues about scheduling overhead and memory‑access patterns.

Key concepts explained:

CPU time : real, user, sys – their ratios indicate compute‑intensive versus I/O‑wait behavior.

Context switches : frequent switches suggest many blocking system calls or high CPU contention.

Page faults : high major faults point to poor memory locality; minor faults are normal.

By correlating these numbers you can pinpoint performance bottlenecks and decide where to optimise – e.g., reducing I/O, improving parallelism, or tuning memory usage.