8.244790 task-clock:u (msec) # 0.033 CPUs utilized ( +- 1.98% ) 0 context-switches:u # 0.000 K/sec 0 cpu-migrations:u # 0.000 K/sec 577 page-faults:u # 0.070 M/sec ( +- 0.18% ) 8,363,454 cycles:u # 1.014 GHz ( +- 1.43% ) 8,053,164 stalled-cycles-frontend:u # 96.29% frontend cycles idle ( +- 2.43% ) 12,952,085 instructions:u # 1.55 insn per cycle # 0.62 stalled cycles per insn ( +- 0.55% ) 2,835,964 branches:u # 343.970 M/sec ( +- 0.73% ) 75,586 branch-misses:u # 2.67% of all branches ( +- 4.21% ) 0.247575641 seconds time elapsed ( +- 28.79% )
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.
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.
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
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: