Execution Timing

Wade asked a question about timing executions; unfortunately a slip
of the fingers marked his post as read and I can't recall it until I
either catch up the group or it appears on google groups...

The execution times I reported in the referenced thread actually
come from the seti@home site -- they are keeping track of the numbers, not
me. In general under Windows I keep an eye on things using Task Manager
for checking the larger picture (that's how I know my securicam is taking
up 4% of my processing power on this machine).

When I do program up code snippets for checking runtimes, I'll either
do it under cygwin on this box, or ssh into the Linux box, because I don't
have Windows compilers to hand. On either I'll use the "time" command to
look at the overall times (that's what I did in the other referenced thread)
or put specific calls to e.g. CPU_TIME() to profile specific areas of the
code.

One could also use gprof to further profile code timings, but I've
not had cause to do that (except once when I started to work on the seti
code, but real life soon intervened...).

--
Ivan Reid, School of Engineering & Design, _____________ CMS Collaboration,
Brunel University. Ivan.Reid@[brunel.ac.uk|cern.ch] Room 40-1-B12, CERN
KotPT -- "for stupidity above and beyond the call of duty".
.