Home/ Questions/Q 7592349
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T20:53:04+00:00

I have some problem using the clock_gettime() function. #include <iostream> #include <time.h> timespec timer_start;

  • 0

I have some problem using the clock_gettime() function. 

#include <iostream>
#include <time.h>

timespec timer_start;
timespec timer_end;

clock_gettime(CLOCK_PROCESS_CPUTIME_ID, &timer_start);
// sleep for 5 seconds
boost::this_thread::sleep(boost::posix_time::milliseconds(5000));
clock_gettime(CLOCK_PROCESS_CPUTIME_ID, &timer_end);

std::cout << (timer_end.tv_sec - timer_start.tv_sec) << ":" << (timer_end.tv_nsec - timer_start.tv_nsec) << std::endl;

The output I get is this

0:6934599

It seems that the timer only elapsed 693 milliseconds or so.

I compile the program with g++ -lrt on Linux gnu gcc 4.6. I also received a Semantic Error, says
Symbol ‘CLOCK_PROCESS_CPUTIME_ID’ could not be resolved

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Leaving aside the impossibility of running a program that fails to compile, sleeping is typically a system call: a kernel function is called, the kernel sends the thread to sleep, schedules other threads and processes to run (or the CPU to enter a power saving mode) and wakes the original thread up again at the requested time. During this time, the sleeping thread will not consume CPU time. The (real) time that elapses is typically referred to as wall time.

    Contrast this to a live wait of a while loop in your code that repeatedly checks the clock and only terminates after 5 seconds have elapsed. This kind of wait will rack up CPU time it takes away from other processes.

    Note also that 6934599 nanoseconds are about 6.93 milliseconds, not 693.

    • 0