take execution time of several commands

time { <command1> ; <command2> ; <command...> ; }
The last ; is important. example: time { rm -rf /folder/bar && mkdir -p /folder/bar ; echo "done" ; } command is a bash builtin
Sample Output
/tmp$ time { du -sh * ; }
4.0K	atievntX.MKIj8U
0	AtiXUEvent00001424_0807cb30
4.0K	keyring-OIEBg3
8.0K	orbit-adminjfu
244K	pdfdownload
20K	plugtmp
20K	plugtmp-1
4.0K	seahorse-7hdOJ8

real	0m0.004s
user	0m0.004s
sys	0m0.000s

By: dizzgo
2009-02-19 16:23:42

What Others Think

I find /bin/time to give more useful (i.e. less verbose) output.
rae · 661 weeks and 1 day ago
send the output of the command to /dev/null , to print only the time command output.
eastwind · 605 weeks and 2 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: