My doubt is something that I believe should be simple for anyone who already develops.
But unfortunately I didn't find the answer on the Stackoverflow platform or even on Google!
Believe me, I found the opposite but nothing about my problem.
My question: There are several ways to get the time in Windows and Linux operating systems, among them some use different techniques, such as CPU or Wall time etc.
But which of the existing techniques for both operating systems have the lowest call cost? That is, can it be called multiple times with little overhead?
Yes, despite finding several answers referring to different precisions and situations, I didn't find any that fit my use case.
Imagine a multi-threaded application that for each action, whether called an endpoint or anything else, needs to register the last hour of execution in a static global variable in integer or long format?
For this reason I want to know which system call, in both (Windows and Linux) have the least overhead.
Observation: Even if it is a hypothetical situation, and does not refer to any real application, please do not comment something like "Don't worry about it, just use whatever", because however true this is, my doubt as explained above it's about a hypothetical example, so if there wasn't the curiosity to know the answer, I wouldn't have posted the question !
I'm trying to satisfy my curiosity and waiting for a scientific answer to the question.
Important Note: The calling method must be in C or C++ language, that is, in javascript you can use new Date().getTime(), among others depending on the language.
But, my question is limited to C/C++ using pure native APIs, ie std::chrono::system_clock::now() doesnt count !
