--opJtzjQTFsWo+cga
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 14, 2006 at 02:13:55PM -0400, Gary Corcoran wrote:
> Mike Meyer wrote:
> >In <45099123.4000500@rcn.com>, Gary Corcoran typed:
> >>The confusing thing is that I thought 'real' time should be >=3D 'user'=

+=20
> >>'sys'.
> >>But here 'user' is much greater than 'real' for both machines! The sen=

se=20
> >>I
> >>got from the other messages in this thread is that 'user' time is somew=

hat
> >>meaningless (i.e. unreliable as a measure) in a multi-CPU and/or=20
> >>hyperthreading
> >>environment. Can you clarify?

> >
> >'real' is wall clock time. 'user' and 'sys' are cpu time. If your
> >process gets all of some cpu, then user + sys will be the same as real
> >time. It's not possible to get more than all of a cpu, so that's a
> >maximum *per cpu*. If you have multiple cpus, the formula you want is
> >'real' * ncpu >=3D 'user' + 'sys'.

>=20
> Thanks to all of you for the responses. The thing that was not clear is
> that despite the printed messages, user (and sys) time are *not* measures
> of time.


Yes they are, they're cumulative amount of time spent executing code
in userland or in the kernel.

Kris

--opJtzjQTFsWo+cga
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFCZscWry0BWjoQKURAmoTAJ9IUXWyMHrayD98p+Gjhq wSFwFxDQCgypZB
exEb6D4GF5WDAm+SwVaMv3s=
=Yqif
-----END PGP SIGNATURE-----

--opJtzjQTFsWo+cga--