cpuConstant
Yes with Turbo Boost, CPU speed is not constant ;) And I think every new CPU should have something like that.
I would expect the cpuConstant go lower as turbo kicks in. But my first run usually gives lower number (faster speed), and consequent executions typically but not always are longer/slower.
In either case it is a problem. Recall recently discussed ThreadDeath issue.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page.
Well, I do have many HashMaps and several kdTrees but the fact that Java kicks in with GC at random times is certainly an issue. The init round should be relatively low CPU event on my bot part.
Strange part is that robocode does not report 37 mS long execution as a skipped turn while my "official" cpuConstant is about 6mS.
Robocode gives robots extra time at the beginning of a round. In addition, most of this time is probably taken away by one-time setup and initialization code, making your calculated CPU constant longer than it should be.
Ok. I see why skipped turn event is not fired. But the wildly fluctuating cpu constants is still under the question. The cpu constant calculation is done within one call: it just long loop with heavy math.
Unless GC kicks in at random I see no explanation for it. The problem that it probably does it during the round as well, since I see wildly fluctuating timing in my profiler.
