> And on sparc chips I don't have the issues that can make the cpu cycle > counter inaccurate or less usable as a timing mechanism. On every machine it's a global counter and so it's subject to false accounting due to process scheduling. That's what CLOCK_THREAD_CPUTIME_ID avoids.