{"id":8089,"date":"2018-12-20T18:48:36","date_gmt":"2018-12-20T15:48:36","guid":{"rendered":"https:\/\/www.howtoforge.com\/linux-time-command\/"},"modified":"2018-12-20T18:48:36","modified_gmt":"2018-12-20T15:48:36","slug":"%d8%a2%d9%85%d9%88%d8%b2%d8%b4-%d8%af%d8%b3%d8%aa%d9%88%d8%b1%d8%a7%d8%aa-%d8%b2%d9%85%d8%a7%d9%86-%d8%af%d8%b1-%d9%84%db%8c%d9%86%d9%88%da%a9%d8%b3","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/%d8%a2%d9%85%d9%88%d8%b2%d8%b4-%d8%af%d8%b3%d8%aa%d9%88%d8%b1%d8%a7%d8%aa-%d8%b2%d9%85%d8%a7%d9%86-%d8%af%d8%b1-%d9%84%db%8c%d9%86%d9%88%da%a9%d8%b3\/","title":{"rendered":"\u0622\u0645\u0648\u0632\u0634 \u062f\u0633\u062a\u0648\u0631\u0627\u062a \u0632\u0645\u0627\u0646 \u062f\u0631 \u0644\u06cc\u0646\u0648\u06a9\u0633"},"content":{"rendered":"
\"\"<\/div>\n

Sometimes, when you’re executing a program, you might want to know its system resource usage. Like how much time the process spent in kernel mode and user mode, and other info.<\/p>\n

Thankfully, there exists a tool – dubbed time<\/strong> – that’s specifically built for this purpose. In this article, we will discuss the basics of the ‘time’ command using some easy to understand examples.<\/p>\n

But before we do that, it’s worth mentioning that all examples in this tutorial have been tested on an Ubuntu 18.04 LTS machine.<\/p>\n

Linux time command<\/h2>\n

The time command in Linux allows you to run programs and summarize their system resource usage. Following is its syntax:<\/p>\n

time [OPTIONS] COMMAND [ARGS]<\/code><\/pre>\n
Here’s how the tool’s man page describes it:<\/p>\n
time run the program COMMAND with any given arguments ARG....\u00a0 When COMMAND finishes, time displays\ninformation about resources used by COMMAND (on the standard error output, by default).\u00a0<\/code><\/pre>\n
If COMMAND exits with non-zero status, time displays a warning message and the exit status.<\/p>\n
<\/code><\/pre>\n
time determines which information to display about the resources used by the COMMAND from the
\nstring FORMAT. If no format is specified on the command line, but the TIME environment variable
\nis set, its value is used as the format. Otherwise, a default format built into time is used.<\/p>\n
<\/code><\/pre>\n
Options to time must appear on the command line before COMMAND.\u00a0 Anything on the command line after
\nCOMMAND is passed as arguments to COMMAND.<\/p>\n
<\/code><\/pre>\n
Following are some Q&A-styled examples that should give you a better idea on how the time command works.<\/p>\n
Q1. How to use time command?<\/h2>\n
The basic usage is simple – just execute ‘time’ with the command\/program you want to run as input.<\/p>\n
For example, I used the time command in the following way:<\/p>\n
time ping howtoforge.com<\/code><\/pre>\n
And here’s the output:<\/p>\n
PING howtoforge.com (104.24.0.68) 56(84) bytes of data.\n64 bytes from 104.24.0.68 (104.24.0.68): icmp_seq=1 ttl=59 time=93.8 ms\n64 bytes from 104.24.0.68 (104.24.0.68): icmp_seq=2 ttl=59 time=91.5 ms\n64 bytes from 104.24.0.68 (104.24.0.68): icmp_seq=3 ttl=59 time=93.1 ms\n64 bytes from 104.24.0.68 (104.24.0.68): icmp_seq=4 ttl=59 time=102 ms\n^C\n--- howtoforge.com ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 3003ms\nrtt min\/avg\/max\/mdev = 91.510\/95.249\/102.490\/4.267 ms<\/code><\/pre>\n
real\u00a0\u00a0 \u00a00m3.472s<\/strong>
\nuser\u00a0\u00a0 \u00a00m0.000s<\/strong>
\nsys\u00a0\u00a0 \u00a00m0.004s<\/strong><\/p>\n
<\/code><\/pre>\n
The last three lines in the output are added by the time command. While ‘real’ signifies the wall clock time the ‘ping’ command took from execution till termination, ‘user’ and ‘sys’ are the time taken by ‘ping’ the user space and kernel space, respectively. Detailed about these three times can be accessed here<\/a>.<\/p>\n
Q2. How to make ‘time’ write its output to a file?<\/h2>\n
If you want the time command to write its output to a file instead of the terminal, use the -o command line option, which expects a file name\/path as input.<\/p>\n
For example:<\/p>\n
\/usr\/bin\/time -o \/home\/himanshu\/time-output.txt ping howtoforge.com<\/code><\/pre>\n
This command will display ping’s output on stdout, while the ‘time’ command output will be written to the text file.<\/p>\n
NOTE<\/strong>: We used \/usr\/bin\/time instead of ‘time’ because the shell built-in time command doesn’t offer the -o option.<\/em><\/p>\n
By default, everytime you run this command, the output file will be overwritten. However, if you want, you can make sure new output is appended by using the -a command line option.<\/p>\n
Q3. How to make time produce detailed output?<\/h2>\n
This can be done using the -v command line option. For example, when I used this option while running ‘time’ with a ‘ping’ command, following details were produced in the ‘time’ command output:<\/p>\n
Command being timed: \"ping howtoforge.com\"\n\u00a0\u00a0 \u00a0User time (seconds): 0.00\n\u00a0\u00a0 \u00a0System time (seconds): 0.00\n\u00a0\u00a0 \u00a0Percent of CPU this job got: 0%\n\u00a0\u00a0 \u00a0Elapsed (wall clock) time (h:mm:ss or m:ss): 0:11.77\n\u00a0\u00a0 \u00a0Average shared text size (kbytes): 0\n\u00a0\u00a0 \u00a0Average unshared data size (kbytes): 0\n\u00a0\u00a0 \u00a0Average stack size (kbytes): 0\n\u00a0\u00a0 \u00a0Average total size (kbytes): 0\n\u00a0\u00a0 \u00a0Maximum resident set size (kbytes): 3064\n\u00a0\u00a0 \u00a0Average resident set size (kbytes): 0\n\u00a0\u00a0 \u00a0Major (requiring I\/O) page faults: 0\n\u00a0\u00a0 \u00a0Minor (reclaiming a frame) page faults: 158\n\u00a0\u00a0 \u00a0Voluntary context switches: 14\n\u00a0\u00a0 \u00a0Involuntary context switches: 0\n\u00a0\u00a0 \u00a0Swaps: 0\n\u00a0\u00a0 \u00a0File system inputs: 0\n\u00a0\u00a0 \u00a0File system outputs: 0\n\u00a0\u00a0 \u00a0Socket messages sent: 0\n\u00a0\u00a0 \u00a0Socket messages received: 0\n\u00a0\u00a0 \u00a0Signals delivered: 0\n\u00a0\u00a0 \u00a0Page size (bytes): 4096\n\u00a0\u00a0 \u00a0Exit status: 0<\/code><\/pre>\n
So you can see the time command produces a lot of other details in this mode.<\/p>\n
Q4. How to customize time command output?<\/h2>\n
The time command also offers a ‘format’ command line option that lets you customize the output of this tool. It provides a set of resource specifiers that you can use to fetch any type of information supported by the ‘time’ command (see previous section).<\/p>\n
For example, the time command in the following execution:<\/p>\n
\/usr\/bin\/time -f \"\\t%C [Command details],\\t%K [Total memory usage],\\t%k [Number of signals process received]\" ping howtoforge.com<\/code><\/pre>\n
produced this output:<\/p>\n
ping howtoforge.com [Command details],\u00a0\u00a0 \u00a00 [Total memory usage],\u00a0\u00a0 \u00a00 [Number of signals process received]<\/code><\/pre>\n
The time command man page contains details related to the format command line option.<\/p>\n","protected":false},"excerpt":{"rendered":"
Sometimes, when you’re executing a program, you might want to know its system resource usage. Like how much time the process spent in kernel mode and user mode, and other info. Thankfully, there exists a tool – dubbed time – that’s specifically built for this purpose. In this article, we will discuss the basics of […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-8089","post","type-post","status-publish","format-standard","hentry","category-36"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/8089","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=8089"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/8089\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=8089"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=8089"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=8089"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}