Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!sgi!shinobu!odin!anchor!olson
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: time() vs gettimeofday()
Message-ID: <1990Sep8.085849.5096@odin.corp.sgi.com>
Date: 8 Sep 90 08:58:49 GMT
References: <9009080837.AA06570@mcirps2.med.nyu.edu>
Sender: news@odin.corp.sgi.com (Net News)
Organization: Silicon Graphics, Inc.  Mountain View, CA
Lines: 22

In <9009080837.AA06570@mcirps2.med.nyu.edu> karron@MCIRPS2.MED.NYU.EDU writes:


| Which is the better time call to use if you only are interested
| in measuring clock seconds ? (not system time, cpu time, but
| real time as measured by a stop watch ).

gettimeofday() will get you down to the system clock resolution,
which is 10 ms by default, but which can be changed to ~1 ms (exact
value depends on the model) by kernel configuration or the ftimer
command.  time() will only give you 1 second resolution.

| How do you know if the Performance Measurement Utilities are installed ?
| I don't remember seeing them on my 3.3 inst tape. Where are they ?

Install eoe2.sw.perf (the ftimer command mentioned above is in
eoe2.sw.usrenv).
--

	Dave Olson

Life would be so much easier if we could just look at the source code.