The output you show is a bit odd, since real time would usually be bigger than the other two.
Real time is wall clock time. (what we could measure with a stopwatch)
User time is the amount of time spend in user-mode within the
Sys is the CPU time spend in the kernel within the process.
So I suppose if the work was done by several processors concurrently, the CPU time would be higher than the elapsed wall clock time.
Was this a concurrent/multi-threaded/parallel type of application?
Just as an example, this is what I get on my Linux system when I issue the
time find . command. As expected the elapsed
real time is much larger than the others on this single user/single core process.
The rule of thumb is:
- real < user: The process is CPU bound and takes advantage of parallel execution on multiple cores/CPUs.
- real ≈ user: The process is CPU bound and takes no advantage of parallel exeuction.
- real > user: The process is I/O bound. Execution on multiple cores would be of little to no advantage.