[To reply replace "Aaron.Sloman.XX" with "A.Sloman"]
I have been getting surprisingly large readings from systime on
linux poplog on a 400 Mhz celeron or 600 Mhz Pentium running RedHat
linux.
E.g. I ran a program on a machine doing nothing else, and it took
about 6 or seven seconds on the faster machine to complete the task, yet
timediff(), which uses systime, recorded about 12 seconds.
On the slower machine it took about 10 seconds, yet timediff said it was
about 30 seconds.
Is it possible that systime is systematically out by a factor of 2 or 3
on linux poplog on intel ?
Has anyone else noticed this?
Does anyone know how to fix systime ?
I wonder if it also affects sys_timer, and therefore lib profile.
Aaron
===
Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
School of Computer Science, The University of Birmingham, B15 2TT, UK
EMAIL A.Sloman AT cs.bham.ac.uk (ReadATas@please !)
PAPERS: http://www.cs.bham.ac.uk/research/cogaff/
TOOLS: http://www.cs.bham.ac.uk/research/poplog/freepoplog.html
|