Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
So I know that clock() measures clock cycles, and thus isn’t very good for measuring time, and I know there are functions like omp_get_wtime() for getting the wall time, but it is frustrating for me that the wall time varies so much, and was wondering if there was some way to measure distinct clock cycles (only one cycle even if more than one thread executed in it). It has to be something relatively simple/native. Thanks
See FreeMemory’s answer to this question for RDTSC if your using x86 which I’ve tested and seems to work fine on my system (mac), but see my answer to this question. Also see the criticism of RDTSC here.
It’s not usually worth it to get down to too low a level of detail though, other bits and pieces of work the computer needs to do will use up clock cycles, so it will vary depending on load. I find
omp_get_wtime()sufficient, though I need to put my code in an extra loop to make sure it takes about a second to ensure consistent results from run to run.