Closed cmorty closed 6 years ago
cpuCycles is what we want to profile since that is based on the number of cycles the CPU actually have been active (e.g. running instructions). Cycles is more or less equivalent with elapsed time (also increase during sleep modes). By changing we would end up getting any sleep-time into the function calls - which I do not think is what we want?
Well it says "elapsed" not "cpu-cycles used". So for me the numbers didn't add up, which was very confusing.
Had to find out at which frequency I can run the timer Interrupt and how much code I can execute. This adds more timing information to the SimpleProfiler/logcalls and always shows cycles instead of intermixing it with cpuCycles.