Timeline for Time Command - Debian Linux Server
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 22, 2012 at 14:06 | comment | added | Darth Android | @sawdust +1 Very true. I was thinking about a simplified system which had 1 CPU and 1 process, but forgot to specify the details as such. | |
| Jun 22, 2012 at 6:14 | comment | added | sawdust | "the CPU can sleep while the program is waiting on something" - Actually it's the program that sleeps (i.e. the scheduler puts the process on the "sleep" or waiting-for-I/O list) while the CPU schedules another program/process or enters the idle loop. If no other process is ready to run, then the idle loop could allow the CPU to enter somekind of low power state. | |
| Jun 21, 2012 at 20:17 | vote | accept | Arpssss | ||
| Jun 21, 2012 at 20:12 | comment | added | Darth Android | @Arpssss I believe they are. Real / elapsed / wall clock time is how long between the start and end of the program, e.g., how long the program took to run (as would be measured by a wall clock, hence the name). This is in contrast to CPU time (user time + system time), which measures how much time the CPU spends actually executing the program, which might be less, since the CPU can sleep while the program is waiting on something, such as user input. | |
| Jun 21, 2012 at 20:00 | comment | added | Arpssss | Thanks a lot. Actually, I am little bit confused with REAL TIME (Or WALL CLOCK TIME) vs ELAPSED TIME. Are they same, I mean WALL CLOCK TIME and ELAPSED TIME ? | |
| Jun 21, 2012 at 19:48 | history | answered | Darth Android | CC BY-SA 3.0 |