Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What does "CPU Time" tell me about the process? Is it the accumulated time the process has run? It sometimes jumps a few seconds and often nothing happens.

alt text

share|improve this question
up vote 3 down vote accepted

Yes, it is "Is it the accumulated time the process has run", and by "run" you mean "actually used the CPU". If you saw it jump and then stagnate, that means the process used the CPU for a few seconds, and then either stopped needing it, or was moved away by the scheduler while other processes used the CPU.

share|improve this answer
Accepting this answer because the other one already got an up-vote. Both explain it well. Ta. – Andrew J. Brehm Dec 6 '10 at 9:47

You have lots of applications running in "parallel", competing for system resources, such as the CPU. CPU time tells you how long a particular process has actively used the CPU while it's been running.

Imagine a process constantly using 10% CPU, and running for 20 minutes. In that time, it will have used roughly 2 minutes of CPU time. If a process is computationally expensive, CPU time will rise much faster, since more "real time" will be spent by CPU on that particular process.

share|improve this answer
So the reason it can go up faster than real time is because more than one core is used? – Andrew J. Brehm Dec 6 '10 at 9:46
@Andrew Yes. You get 1 second CPU time per second real time if you have 100% CPU usage, and of course more, if you're above 100% CPU usage (i.e. multiple cores used for a total sum of "more than one core"). – Daniel Beck Dec 6 '10 at 10:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .