CPU time Vs WALL time, Sometimes Walltime lesser than Cputime ?

[anto.anish]

Hi -

I have been using clock() for calculating CPU time and time() for
calculating Wall time. However, since time() does not provided milli/
microsecond accurancy, i started using gettimeofday() as below to
calculate walltime,

struct timeval tv1,tv2;
struct timezone tz1, tz2;
gettimeofday(&t v1,&tz1);
double time_start1 = (double) tv1.tv_sec + (double)tv1.tv_ usec/
1000000.0;
//ALL ALGO PROCESSING HERE
gettimeofday(&t v2,&tz2);
double time_stop1 = (double) tv2.tv_sec + (double)tv2.tv_ usec/
1000000.0;
LOGGER.info("Ba ckgroundEstimat ionAlgoT Run WALL_TIME: %0.3f",(double)
(time_stop1 - time_start1));

Certain times, i have been noticing that WALLTIME calculated is lesser
than CPUTIME. I am not sure why ? Double checked the simple code,
nothing seems to be wrong in simple substraction. My understanding was
always WALLTIME(elapse d time) remains higher than CPUTIME(compute
time).

I test my application on a Linux cluster with 24 compute nodes.
Any pointers as to why is this happening ?

Thanks
Anish

[Victor Bazarov]

an********@gmai l.com wrote:

Hi -

I have been using clock() for calculating CPU time and time() for
calculating Wall time. However, since time() does not provided milli/
microsecond accurancy, i started using gettimeofday() as below to
calculate walltime,

struct timeval tv1,tv2;
struct timezone tz1, tz2;
gettimeofday(&t v1,&tz1);
double time_start1 = (double) tv1.tv_sec + (double)tv1.tv_ usec/
1000000.0;
//ALL ALGO PROCESSING HERE
gettimeofday(&t v2,&tz2);
double time_stop1 = (double) tv2.tv_sec + (double)tv2.tv_ usec/
1000000.0;
LOGGER.info("Ba ckgroundEstimat ionAlgoT Run WALL_TIME: %0.3f",(double)
(time_stop1 - time_start1));

Certain times, i have been noticing that WALLTIME calculated is lesser
than CPUTIME. I am not sure why ? Double checked the simple code,
nothing seems to be wrong in simple substraction. My understanding was
always WALLTIME(elapse d time) remains higher than CPUTIME(compute
time).

I test my application on a Linux cluster with 24 compute nodes.
Any pointers as to why is this happening ?

A few initial points...

Linux-specific questions belong to a Linux newsgroup.

'gettimeofday' is a non-standard function.

If your system has more than one logical CPU or your CPU is capable of
executing more than one instruction at a time, it is generally possible
to get more total CPU seconds than run-time, AIUI.

And the last one: what's your C++ language question?

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask

[James Kanze]

On Oct 17, 10:07*pm, anto.an...@gmai l.com wrote:

Hi -

I have been using clock() for calculating CPU time and time()
for calculating Wall time. However, *since time() does not
provided milli/ microsecond accurancy, i started using
gettimeofday() as below to calculate walltime,

struct timeval tv1,tv2;
struct timezone tz1, tz2;
gettimeofday(&t v1,&tz1);
double time_start1 = (double) tv1.tv_sec + (double)tv1.tv_ usec/
1000000.0;
//ALL ALGO PROCESSING HERE
gettimeofday(&t v2,&tz2);
double time_stop1 = (double) tv2.tv_sec + (double)tv2.tv_ usec/
1000000.0;
LOGGER.info("Ba ckgroundEstimat ionAlgoT Run WALL_TIME: %0.3f",(double)
(time_stop1 - time_start1));

Certain times, i have been noticing that WALLTIME calculated
is lesser than CPUTIME. I am not sure why ? Double checked the
simple code, nothing seems to be wrong in simple substraction.
My understanding was always WALLTIME(elapse d time) remains
higher than CPUTIME(compute time).

You don't seem to be measuring CPU time at all here, so I'm not
sure what you're comparing. Clock() is supposed to return CPU
time, to the systems best approximation: it doesn't always, and
there will be some jitter, so it's quite possible for
differences of clock() to return a value larger than the
differences between to calls to time() (or gettimeofday()) . The
differences shouldn't normally be very larger, however.

I test my application on a Linux cluster with 24 compute
nodes.

That could also affect things, if you were running multiple
threads. I would expect (but the standard doesn't say anything
about it) that clock() would be the sum of the times spent in
two threads.

--
James Kanze (GABI Software) email:ja******* **@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientier ter Datenverarbeitu ng
9 place Sémard, 78210 St.-Cyr-l'École, France, [phone]