Interpreting UNIX time function

Hi all. I suppose this question could have gone in Linux just as well, but it really is a UNIX function, if I'm not mistaken. I've been benchmarking (or trying to) a quick little program I wrote, call it "benchmark," that receives one command-line integer. But I'm still rather unfamiliar with UNIX / Linux platforms, so I'm not entirely sure what all of the nonsense that the time function throws back at me actually represents. I execute this command (where n is some integer):
    time benchmark n

Here are some examples of output that I've gotten back:
1.676u 0.002s 0:01.67 100.0%      0+0k 0+0io 0pf+0w
1.697u 0.011s 0:01.70 100.0%      0+0k 0+0io 0pf+0w
1.704u 0.011s 0:01.71 100.0%      0+0k 0+0io 0pf+0w
1.735u 0.011s 0:01.74 100.0%      0+0k 0+0io 0pf+0w

I counted seven things that are output in each test. I believe the first one is the time it took to execute the program in seconds (although I don't know why it's followed by a 'u'), but I don't know what the last six represent, and the man page didn't make much sense to me. What does all that mumbo-jumbo mean? Please explain the remaining six output parameters.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The gnu version of the time command puts out several statistics.  They are explained here:
soapergemAuthor Commented:
I don't speak man pages. Can someone explain what those mean in English?
> I don't speak man pages.

The man pages are the definitive documentation for unix commands.
They are not cryptic and are generally written in English.   You should
really put the smallest amount of effort into reading them.  In this case
the fields printed are [ in left to right order ]:

Total number of CPU-seconds that the process spent in user mode.
Total number of CPU-seconds that the process spent in kernel mode.
Elapsed real time (in [hours:]minutes:seconds).
Percentage of the CPU that this job got.
Average size of the process's shared text space (the executable code), in Kbytes + Average size of the process's unshared data area, in Kbytes.
Number of file system inputs by the process + Number of file system outputs by the process.
Number of major page faults that occurred while the process was running.  These are faults where the page has to be read in from disk. +
Number of waits:  times that the program was context-switched voluntarily, for instance while waiting for an I/O operation to complete.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.