[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: priorities

On Thu, 06 Dec 2007 13:34:10 -0800, Ben Pfaff <blp@cs.stanford.edu> said: 

> I use "time" in benchmarking scripts. 

        I do not find the built in time to be a substitute for the good
 old fashioned time command. Observe:

__> time sleep 20
Real: 20.03s User: 0.00s System: 0.00s Percent: 0% Cmd: sleep 20
__> /usr/bin/time sleep 20
0.00user 0.00system 0:20.01elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+188minor)pagefaults 0swaps
__> time -v sleep 2       
zsh: command not found: -v
[3]    4136 exit 127   -v sleep 2
Real: 0.00s User: 0.00s System: 0.00s Percent: 0% Cmd: -v sleep 2
__> /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
        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): 0
        Average resident set size (kbytes): 0
        Major (requiring I/O) page faults: 0
        Minor (reclaiming a frame) page faults: 192
        Voluntary context switches: 3
        Involuntary context switches: 0
        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

Men never make passes at girls wearing glasses. Dorothy Parker
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: