4 ms·

Thanks for this! Another nice thing about /usr/bin/time is the --verbose flag which gives: Command being timed: "ls" User time (seconds): 0.00 System ti

by tuldia 7y ago

Thanks for this! Another nice thing about /usr/bin/time is the --verbose flag which gives: Command being timed: "ls" 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:00.00 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 1912 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 0 Minor (reclaiming a frame) page faults: 112 Voluntary context switches: 1 Involuntary context switches: 1 Swaps: 0 File system inputs: 0 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0 :)

yingw787 7y ago
Wow this looks amazing! I didn’t know time could track all of those!
- vaingloriole 7y ago
  man getrusage
boyter 7y ago
Can anyone comment why you can only use the verbose flag if you use the full path of time? time -v ls does not work but /usr/bin/time -v ls does? I don't have enough knowledge of either linux applications or bash to know whats happening to cause this.
- eesmith 7y ago
  Your shell has a built-in "time" command. man bash: If the time reserved word precedes a pipeline, the elapsed as well as user and system time consumed by its execution are reported when the pipeline terminates. man time: Some shells may provide a builtin time command which is similar or identical to this utility. Consult the builtin(1) manual page.
- dtwwtd 7y ago
  This is very likely because without the full path your shell is using the `time` builtin function of your shell as opposed to using the binary. The shell's builtin keyword for `time` is more limited in nature than the full `time` binary. This is true of a number of other common unix commands as well, e.g. `echo`. The manpage for your shell should describe the builtins functions.
- amypinka 7y ago
  The full path calls a GNU tool, the other calls your shell's builtin function.
- inimino 7y ago
  You can also type `type time` to see that time is a builtin. `which` and `hash` may also be interesting.
- deleted 7y ago
  [deleted]
- tuldia 7y ago
  You can also use: \time -v ls to skip the builtin version.

by tuldia 7y ago

yingw787 7y ago

Wow this looks amazing! I didn’t know time could track all of those!

vaingloriole 7y ago
man getrusage

boyter 7y ago

Can anyone comment why you can only use the verbose flag if you use the full path of time? time -v ls does not work but /usr/bin/time -v ls does? I don't have enough knowledge of either linux applications or bash to know whats happening to cause this.

eesmith 7y ago
Your shell has a built-in "time" command. man bash: If the time reserved word precedes a pipeline, the elapsed as well as user and system time consumed by its execution are reported when the pipeline terminates. man time: Some shells may provide a builtin time command which is similar or identical to this utility. Consult the builtin(1) manual page.
dtwwtd 7y ago
This is very likely because without the full path your shell is using the `time` builtin function of your shell as opposed to using the binary. The shell's builtin keyword for `time` is more limited in nature than the full `time` binary. This is true of a number of other common unix commands as well, e.g. `echo`. The manpage for your shell should describe the builtins functions.
amypinka 7y ago
The full path calls a GNU tool, the other calls your shell's builtin function.
inimino 7y ago
You can also type `type time` to see that time is a builtin. `which` and `hash` may also be interesting.
deleted 7y ago
[deleted]
tuldia 7y ago
You can also use: \time -v ls to skip the builtin version.