Question

I was trying to program a Timer class (unaware that boost had one), then when that wasn’t working, I tried to just output the value of clock(), using this code:

#include <ctime>
#include <iostream>

int main()
{
 for(int i = 0; i < 50; ++i)
 {
  std::cout << std::clock() << " ";
 }
 return 0;
}

When I run the program, I get a series of 0s. I have a similar experience when using boost thread sleep functions to spread out timing a little longer (although after a few seconds, it jumps from 0 to 10,000 and keeps outputting 10,000).

I’m running Gentoo Linux. Is this a platform thing? A C++ thing? What’s going on?

Edit: Strangely the jump to 10000 comes after a number of seconds, not milliseconds. When I was sleeping my thread for a second at a time, it took five or six seconds to get to 10000. However, if I’m understanding correctly. The time the thread spends sleeping doesn’t contribute towards the clock() count? (Which would make sense; why would it be executing clock cycles if it’s sleeping?)

Answer 1

The clock() return value is specified in microseconds. But typical granularity of whatever low-level system call the clock() implementation uses is much lower. So it seems that on your system the granularity is 10ms. Also note that clock() does NOT measure real time – it measures CPU time used by the program. So the time flows when your program controls the CPU, and it freezes when your program is suspended – sleeping, for example.