cpuConstant
From User talk:Beaming
Jump to navigation
Jump to search
Revision as of 17 October 2017 at 02:37.
This is the thread's initial revision.
This is the thread's initial revision.
Hi all, I decided to work on my skipped turns and to watch my execution time. As the first step, I recalculated cpuConstant according to cpuManager code (I wish it would be available from within the robot) at the beginning of each round. Guess what. The number wildly fluctuate. By wildly, we are talkin more than FOUR times!!! On the short end of the spectrum cpuConstant is about 8mS and it can be as large as 35mS.
Any ideas what is going on? Everything is done with openjdk8. One difference from the original code: I measure time with System.nanoTime()